CVE-2017-18106

published 29 Mar 2019 · updated 16 Sep 2024

The identifier_hash for a session token in Atlassian Crowd before version 2.9.1 could potentially collide with an identifier_hash for…

5.0MediumEPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Crowd 2.9.1.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
AtlassianCrowd<2.9.12.9.1

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Atlassian, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2017-18106 severity on Zeptric[![CVE-2017-18106](https://zeptric.io/badge/cve/CVE-2017-18106.svg)](https://zeptric.io/cve/CVE-2017-18106)