How severe is CVE-2017-14590?

CVE-2017-14590 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-14590 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-14590?

CVE-2017-14590 affects Atlassian Bamboo. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-14590?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2017-14590 published?

CVE-2017-14590 was published on 2017-12-13 and last updated on 2026-06-17.

CVE-2017-14590

CVE-2017-14590 is a critical-severity vulnerability in Atlassian Bamboo with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
CVSS v2: 9.0
EPSS exploit prediction: 2% (82nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Atlassian Bamboo
Published: 2017-12-13
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2017-14590?: 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.
How severe is CVE-2017-14590?: CVE-2017-14590 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-14590 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-14590?: CVE-2017-14590 affects Atlassian Bamboo. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-14590?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-14590 published?: CVE-2017-14590 was published on 2017-12-13 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:atlassian:bamboo:*:*:*:*:*:*:*:*

More vulnerabilities in Atlassian Bamboo

CVE-2022-26136 — Critical (CVSS 9.8): A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to bypass Servlet Filters used…
CVE-2016-5229 — Critical (CVSS 9.8): Atlassian Bamboo before 5.11.4.1 and 5.12.x before 5.12.3.1 does not properly restrict permitted deserialized classes,…
CVE-2015-8360 — Critical (CVSS 9.8): An unspecified resource in Atlassian Bamboo before 5.9.9 and 5.10.x before 5.10.0 allows remote attackers to execute…
CVE-2014-9757 — Critical (CVSS 9.8): The Ignite Realtime Smack XMPP API, as used in Atlassian Bamboo before 5.9.9 and 5.10.x before 5.10.0, allows remote…
CVE-2017-14589 — Critical (CVSS 9.6): It was possible for double OGNL evaluation in FreeMarker templates through Struts FreeMarker tags to occur. An attacker…
CVE-2015-8361 — Critical (CVSS 9.1): Multiple unspecified services in Atlassian Bamboo before 5.9.9 and 5.10.x before 5.10.0 do not require authentication,…

All CVEs affecting Atlassian Bamboo →