{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-14590 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-14590 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-14590 is a critical command injection vulnerability in Atlassian Bamboo, published on 13 Dec 2017. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-14590 and fix it if it is affected.\n\nWhat it is: CVE-2017-14590 is a critical command injection vulnerability in Atlassian Bamboo, published on 13 Dec 2017. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-14590 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-14590/ (Markdown: https://insights.sbomify.com/CVE-2017-14590/index.md)","id":"CVE-2017-14590","markdown":"https://insights.sbomify.com/CVE-2017-14590/index.md","name":"CVE-2017-14590","record":{"aliases":["GHSA-6qp2-wv9g-xq2p"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Bamboo","requires_auth":"high_privilege","summary":"An attacker with specific repository permissions can execute arbitrary code on the Bamboo server by injecting arguments into Mercurial branch names.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"bamboo","vendor":"atlassian"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Bamboo did not check that the name of a branch in a Mercurial repository contained argument parameters. An attacker who has permission to create a repository in Bamboo, edit an existing plan that has a non-linked Mercurialrepository, create or edit a plan when there is at least one linked Mercurial repository that the attacker has permission to use, or commit to a Mercurial repository used by a Bamboo plan which has branch detection enabled can execute code of their choice on systems that run a vulnerable version of Bamboo Server. Versions of Bamboo starting with 2.7.0 before 6.1.6 (the fixed version for 6.1.x) and from 6.2.0 before 6.2.5 (the fixed version for 6.2.x) are affected by this 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":"Command injection in Bamboo","id":"CVE-2017-14590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in Fisheye and Crucible","id":"CVE-2017-14591"},"packages":[],"prev":{"headline":"Code injection in Bamboo","id":"CVE-2017-14589"},"products":["Bamboo"],"published":"2017-12-13","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Atlassian"]},"summary":"An attacker with specific repository permissions can execute arbitrary code on the Bamboo server by injecting arguments into Mercurial branch names.","url":"https://insights.sbomify.com/CVE-2017-14590/"}