A vulnerability, which was classified as critical, was found in Atlassian Crowd up to 2.9.0. This affects an unknown functionality of the component Session Identifier. The manipulation as part of a Session Token leads to a improper authentication vulnerability (Collision). CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared 03/29/2019. This vulnerability is uniquely identified as CVE-2017-18106 since 02/01/2018. The exploitability is told to be difficult. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. Neither technical details nor an exploit are publicly available.

Upgrading to version 2.9.1 eliminates this vulnerability.

The entries 132612, 132611, 132610 and 132608 are related to this item.

Productinfo

Name

• Atlassian Crowd

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion