{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18109 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18109 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18109 is a medium-severity vulnerability in Atlassian Crowd, published on 29 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-18109 and fix it if it is affected.\n\nWhat it is: CVE-2017-18109 is a medium-severity vulnerability in Atlassian Crowd, published on 29 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-18109 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-18109/ (Markdown: https://insights.sbomify.com/CVE-2017-18109/index.md)","id":"CVE-2017-18109","markdown":"https://insights.sbomify.com/CVE-2017-18109/index.md","name":"CVE-2017-18109","record":{"aliases":["GHSA-3jv4-c99q-p2j6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Crowd","requires_auth":"none","summary":"Remote attackers can redirect users to malicious sites via the login resource, facilitating phishing attacks against Atlassian Crowd users.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"crowd","vendor":"atlassian"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"The login resource of CrowdId in Atlassian Crowd before version 3.0.2 and from version 3.1.0 before version 3.1.1 allows remote attackers to redirect users to a different website which they may use as part of performing a phishing attack via an open redirect.","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":"Open redirect in Crowd","id":"CVE-2017-18109","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"XML external entity in Crowd","id":"CVE-2017-18110"},"packages":[],"prev":{"headline":"Code injection in Crowd","id":"CVE-2017-18108"},"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-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-16","vendors":["Atlassian"]},"summary":"Remote attackers can redirect users to malicious sites via the login resource, facilitating phishing attacks against Atlassian Crowd users.","url":"https://insights.sbomify.com/CVE-2017-18109/"}