{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16858 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16858 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16858 is a medium-severity authentication bypass vulnerability in Atlassian Crowd, published on 31 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16858 and fix it if it is affected.\n\nWhat it is: CVE-2017-16858 is a medium-severity authentication bypass vulnerability in Atlassian Crowd, published on 31 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-16858 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-16858/ (Markdown: https://insights.sbomify.com/CVE-2017-16858/index.md)","id":"CVE-2017-16858","markdown":"https://insights.sbomify.com/CVE-2017-16858/index.md","name":"CVE-2017-16858","record":{"aliases":["GHSA-p3gx-g437-gw6c"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Atlassian Crowd","requires_auth":"low_privilege","summary":"Attackers can impersonate users across directories in Atlassian Crowd by exploiting authentication flaws in the crowd-application plugin, requiring specific directory bindings.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"crowd","vendor":"atlassian"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The 'crowd-application' plugin module (notably used by the Google Apps plugin) in Atlassian Crowd from version 1.5.0 before version 3.1.2 allowed an attacker to impersonate a Crowd user in REST requests by being able to authenticate to a directory bound to an application using the feature. Given the following situation: the Crowd application is bound to directory 1 and has a user called admin and the Google Apps application is bound to directory 2, which also has a user called admin, it was possible to authenticate REST requests using the credentials of the user coming from directory 2 and impersonate the user from directory 1.","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-16858","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":"Path traversal in Fisheye and Crucible","id":"CVE-2017-16859"},"packages":[],"prev":{"headline":"Race condition in Auto-Unapprove Plugin (for Bitbucket Server)","id":"CVE-2017-16857"},"products":["Crowd"],"published":"2018-01-31","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-2017-18105","kev_date_added":null,"published":"2019-03-29"},{"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-17","vendors":["Atlassian"]},"summary":"Attackers can impersonate users across directories in Atlassian Crowd by exploiting authentication flaws in the crowd-application plugin, requiring specific directory bindings.","url":"https://insights.sbomify.com/CVE-2017-16858/"}