CVE-2017-18106

Description

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.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.57%
Vendor Advisory atlassian.com
Affected: Atlassian Crowd
Published at:
Updated at:

References

Link Tags
https://jira.atlassian.com/browse/CWD-5061 issue tracking vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-18106?
CVE-2017-18106 has been scored as a high severity vulnerability.
How to fix CVE-2017-18106?
To fix CVE-2017-18106, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-18106 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-18106 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-18106?
CVE-2017-18106 affects Atlassian Crowd.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.