CVE-2017-18106: Atlassian Crowd vulnerability
Atlassian · Crowd
Fixed in 2.9.1 · Affected: Atlassian Crowd before 2.9.1 · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 69% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
The identifier_hash for a session token in Atlassian Crowd before version 2.9.1 could potentially collide with an identifier_hash for another user or a user in a different directory, this allows remote attackers who can authenticate to Crowd or an application using Crowd for authentication to gain access to another user's session provided they can make their identifier hash collide with another user's session identifier hash.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Atlassian · Crowdbefore 2.9.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Atlassian
- Published
- March 2019
CoverageNo articles yet
No CyberSIXT article names CVE-2017-18106 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.