{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18040 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18040 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18040 is a medium-severity cross-site scripting vulnerability in Atlassian Bamboo, published on 2 Feb 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-18040 and fix it if it is affected.\n\nWhat it is: CVE-2017-18040 is a medium-severity cross-site scripting vulnerability in Atlassian Bamboo, published on 2 Feb 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-18040 in the wild and no public exploit code.\n\nAffected product: Atlassian Bamboo. 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-18040/ (Markdown: https://insights.sbomify.com/CVE-2017-18040/index.md)","id":"CVE-2017-18040","markdown":"https://insights.sbomify.com/CVE-2017-18040/index.md","name":"CVE-2017-18040","record":{"aliases":["GHSA-5g4x-4hfv-6v46"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Bamboo","requires_auth":"low_privilege","summary":"Remote attackers can inject arbitrary HTML or JavaScript via the release name in Atlassian Bamboo, potentially leading to session hijacking or malicious actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"bamboo","vendor":"atlassian"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The viewDeploymentVersionCommits resource in Atlassian Bamboo before version 6.2.0 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the name of a release.","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":"Cross-site scripting in Bamboo","id":"CVE-2017-18040","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Bamboo","id":"CVE-2017-18041"},"packages":[],"prev":{"headline":"Cross-site scripting in Jira","id":"CVE-2017-18039"},"products":["Bamboo"],"published":"2018-02-02","related":[{"cvss_score":9.3,"headline":"Atlassian Multiple Products Files or Directories Accessible to External Parties","id":"CVE-2026-21589","kev_date_added":"2026-10-15","published":"2026-10-05"},{"cvss_score":9.8,"headline":"Auth bypass in Bamboo Data Center","id":"CVE-2022-26136","kev_date_added":null,"published":"2022-07-20"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2016-5229","kev_date_added":null,"published":"2016-08-02"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2014-9757","kev_date_added":null,"published":"2016-02-08"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2015-8360","kev_date_added":null,"published":"2016-02-08"},{"cvss_score":9.6,"headline":"Code injection in Bamboo","id":"CVE-2017-14589","kev_date_added":null,"published":"2017-12-13"},{"cvss_score":9.4,"headline":"Command injection in Bamboo Data Center","id":"CVE-2026-21571","kev_date_added":null,"published":"2026-04-21"}],"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 inject arbitrary HTML or JavaScript via the release name in Atlassian Bamboo, potentially leading to session hijacking or malicious actions.","url":"https://insights.sbomify.com/CVE-2017-18040/"}