{"api_version":"1","generated_at":"2026-07-24T02:45:39+00:00","cve":"CVE-2017-18106","urls":{"html":"https://cve.report/CVE-2017-18106","api":"https://cve.report/api/cve/CVE-2017-18106.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2017-18106","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2017-18106"},"summary":{"title":"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.","state":"PUBLIC","assigner":"security@atlassian.com","published_at":"2019-03-29 14:29:00","updated_at":"2019-04-01 14:06:00"},"problem_types":["CWE-287"],"metrics":[],"references":[{"url":"https://jira.atlassian.com/browse/CWD-5061","name":"https://jira.atlassian.com/browse/CWD-5061","refsource":"MISC","tags":["Issue Tracking","Vendor Advisory"],"title":"[CWD-5061] Session hijacking due to token identifier hash collision - CVE-2017-18106 - Create and track feature requests for Atlassian products.","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-18106","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-18106","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2017","cve_id":"18106","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"atlassian","cpe5":"crowd","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2017","cve_id":"18106","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"atlassian","cpe5":"crowd","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security@atlassian.com","DATE_PUBLIC":"2019-03-04T00:00:00","ID":"CVE-2017-18106","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"Crowd","version":{"version_data":[{"version_value":"2.9.1","version_affected":"<"}]}}]},"vendor_name":"Atlassian"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"Use of a Broken or Risky Cryptographic Algorithm"}]}]},"references":{"reference_data":[{"url":"https://jira.atlassian.com/browse/CWD-5061","refsource":"MISC","name":"https://jira.atlassian.com/browse/CWD-5061"}]}},"nvd":{"publishedDate":"2019-03-29 14:29:00","lastModifiedDate":"2019-04-01 14:06:00","problem_types":["CWE-287"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":7.5,"baseSeverity":"HIGH"},"exploitabilityScore":1.6,"impactScore":5.9},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:S/C:P/I:P/A:P","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"SINGLE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"PARTIAL","baseScore":6},"severity":"MEDIUM","exploitabilityScore":6.8,"impactScore":6.4,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:atlassian:crowd:*:*:*:*:*:*:*:*","versionEndExcluding":"2.9.1","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2017","CveId":"18106","Ordinal":"122599","Title":"CVE-2017-18106","CVE":"CVE-2017-18106","Year":"2017"},"notes":[{"CveYear":"2017","CveId":"18106","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2017","CveId":"18106","Ordinal":"2","NoteData":"2019-03-29","Type":"Other","Title":"Published"},{"CveYear":"2017","CveId":"18106","Ordinal":"3","NoteData":"2019-03-29","Type":"Other","Title":"Modified"}]}}}