How severe is CVE-2017-9514?

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

Is CVE-2017-9514 being actively exploited?

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

What products are affected by CVE-2017-9514?

CVE-2017-9514 primarily affects Atlassian Bamboo. In total, 8 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-9514?

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

When was CVE-2017-9514 published?

CVE-2017-9514 was published on 2017-10-12 and last updated on 2026-06-17.

CVE-2017-9514

CVE-2017-9514 is a high-severity vulnerability in Atlassian Bamboo with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-732.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.5
EPSS exploit prediction: 1% (60th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-732
Affected product: Atlassian Bamboo
Published: 2017-10-12
Last modified: 2026-06-17

Description

Bamboo before 6.0.5, 6.1.x before 6.1.4, and 6.2.x before 6.2.1 had a REST endpoint that parsed a YAML file and did not sufficiently restrict which classes could be loaded. An attacker who can log in to Bamboo as a user is able to exploit this vulnerability to execute Java code of their choice on systems that have vulnerable versions of Bamboo.

Frequently asked questions

What is CVE-2017-9514?: Bamboo before 6.0.5, 6.1.x before 6.1.4, and 6.2.x before 6.2.1 had a REST endpoint that parsed a YAML file and did not sufficiently restrict which classes could be loaded. An attacker who can log in to Bamboo as a user is able to exploit this vulnerability to execute Java code of their choice on systems that have vulnerable versions of Bamboo.
How severe is CVE-2017-9514?: CVE-2017-9514 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-9514 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (60th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-9514?: CVE-2017-9514 primarily affects Atlassian Bamboo. In total, 8 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-9514?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-9514 published?: CVE-2017-9514 was published on 2017-10-12 and last updated on 2026-06-17.

References

Affected products (8)

cpe:2.3:a:atlassian:bamboo:6.0.0:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:bamboo:6.0.1:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:bamboo:6.0.2:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:bamboo:6.0.3:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:bamboo:6.0.4:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:bamboo:6.1.0:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:bamboo:6.1.1:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:bamboo:6.2.0:*:*:*:*:*:*:*

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-2017-14590 — Critical (CVSS 9.1): Bamboo did not check that the name of a branch in a Mercurial repository contained argument parameters. An attacker who…

All CVEs affecting Atlassian Bamboo →

Other CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities

CVE-2026-9508 — Critical (CVSS 10.0): Incorrect permission settings on a critical resource in Suprema BioStar 2 (versions 2.9.3 through 2.9.11) that allow…
CVE-2025-14988 — Critical (CVSS 10.0): A security issue has been identified in ibaPDA that could allow unauthorized actions on the file system under certain…
CVE-2025-69426 — Critical (CVSS 10.0): The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) contain hardcoded credentials for an operating…
CVE-2025-12004 — Critical (CVSS 10.0): Incorrect Permission Assignment for Critical Resource vulnerability in The Wikimedia Foundation Mediawiki - Lockdown…
CVE-2014-125121 — Critical (CVSS 10.0): Array Networks vAPV (version 8.3.2.17) and vxAG (version 9.2.0.34) appliances are affected by a privilege escalation…
CVE-2025-46093 — Critical (CVSS 9.9): LiquidFiles before 4.1.2 supports FTP SITE CHMOD for mode 6777 (setuid and setgid), which allows FTPDrop users to…

Browse all CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities →