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.
Published 2019-03-29 14:29:00
Updated 2019-04-01 14:06:34
Source Atlassian
View at NVD,   CVE.org
Vulnerability category: BypassGain privilege

Products affected by CVE-2017-18106

Exploit prediction scoring system (EPSS) score for CVE-2017-18106

0.23%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 60 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2017-18106

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
6.0
MEDIUM AV:N/AC:M/Au:S/C:P/I:P/A:P
6.8
6.4
NIST
7.5
HIGH CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
1.6
5.9
NIST

CWE ids for CVE-2017-18106

  • When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
    Assigned by: nvd@nist.gov (Primary)

References for CVE-2017-18106

  • https://jira.atlassian.com/browse/CWD-5061
    [CWD-5061] Session hijacking due to token identifier hash collision - CVE-2017-18106 - Create and track feature requests for Atlassian products.
    Issue Tracking;Vendor Advisory
Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!