CVE-2017-18106
First published: Fri Mar 29 2019(Updated: )
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.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Crowd | <2.9.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2017-18106?
CVE-2017-18106 is a vulnerability in Atlassian Crowd before version 2.9.1 that allows remote attackers to gain unauthorized access.
What is the severity of CVE-2017-18106?
CVE-2017-18106 has a severity rating of 7.5 (high).
How does CVE-2017-18106 work?
CVE-2017-18106 occurs when the identifier_hash for a session token in Atlassian Crowd collides with an identifier_hash for another user or a user in a different directory, allowing remote attackers to gain unauthorized access.
Which software versions are affected by CVE-2017-18106?
CVE-2017-18106 affects Atlassian Crowd versions up to, but excluding, 2.9.1.
How can I fix CVE-2017-18106?
To fix CVE-2017-18106, update to Atlassian Crowd version 2.9.1 or later.
- collector/nvd-index
- vendor/atlassian
- canonical/atlassian crowd