{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18105 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18105 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18105 is a high-severity authentication bypass vulnerability in Atlassian Crowd, published on 29 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-18105 and fix it if it is affected.\n\nWhat it is: CVE-2017-18105 is a high-severity authentication bypass vulnerability in Atlassian Crowd, published on 29 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-18105 in the wild and no public exploit code.\n\nAffected product: Atlassian Crowd. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-18105/ (Markdown: https://insights.sbomify.com/CVE-2017-18105/index.md)","id":"CVE-2017-18105","markdown":"https://insights.sbomify.com/CVE-2017-18105/index.md","name":"CVE-2017-18105","record":{"aliases":["GHSA-qq79-32v4-8c7v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Crowd","requires_auth":"none","summary":"Attackers with a stolen session ID can bypass authentication to access protected resources in Atlassian Crowd.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"crowd","vendor":"atlassian"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-384","name":"Session Fixation"}],"description":"The console login resource in Atlassian Crowd before version 3.0.2 and from version 3.1.0 before version 3.1.1 allows remote attackers, who have previously obtained a user's JSESSIONID cookie, to gain access to some of the built-in and potentially third party rest resources via a session fixation vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in Crowd","id":"CVE-2017-18105","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in Crowd","id":"CVE-2017-18106"},"packages":[],"prev":{"headline":"Information disclosure in Jira","id":"CVE-2017-18104"},"products":["Crowd"],"published":"2019-03-29","related":[{"cvss_score":9.8,"headline":"Atlassian Crowd and Crowd Data Center Remote Code Execution","id":"CVE-2019-11580","kev_date_added":"2021-11-03","published":"2019-06-03"},{"cvss_score":9.8,"headline":"Auth bypass in Crowd Data Center","id":"CVE-2022-43782","kev_date_added":null,"published":"2022-11-17"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2016-6496","kev_date_added":null,"published":"2016-12-09"},{"cvss_score":8.1,"headline":"Auth bypass in Crowd","id":"CVE-2018-20238","kev_date_added":null,"published":"2019-02-13"},{"cvss_score":8,"headline":"Code injection in Crowd Data Center","id":"CVE-2023-22521","kev_date_added":null,"published":"2023-11-21"},{"cvss_score":7.9,"headline":"XML external entity in Crowd Data Center","id":"CVE-2026-21569","kev_date_added":null,"published":"2026-01-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Atlassian"]},"summary":"Attackers with a stolen session ID can bypass authentication to access protected resources in Atlassian Crowd.","url":"https://insights.sbomify.com/CVE-2017-18105/"}