# CVE-2017-9514: Deserialization in Bamboo

> Authenticated attackers can execute arbitrary Java code via unsafe YAML deserialization in Atlassian Bamboo REST endpoints.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2rqq-cg89-vq87

## What is CVE-2017-9514?

CVE-2017-9514 is a high-severity unsafe deserialization vulnerability in Atlassian Bamboo, published on 12 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-9514?

It affects 1 product.


Products: Atlassian Bamboo.

## How do I fix CVE-2017-9514?

No fix has been published for CVE-2017-9514 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9514 being exploited?

There is no known exploitation of CVE-2017-9514 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Bamboo

- [CVE-2026-21589](https://insights.sbomify.com/CVE-2026-21589/): Atlassian Multiple Products Files or Directories Accessible to External Parties (critical 9.3, exploited in the wild)
- [CVE-2022-26136](https://insights.sbomify.com/CVE-2022-26136/): Auth bypass in Bamboo Data Center (critical 9.8)
- [CVE-2016-5229](https://insights.sbomify.com/CVE-2016-5229/): Deserialization in n/a (critical 9.8)
- [CVE-2014-9757](https://insights.sbomify.com/CVE-2014-9757/): Deserialization in n/a (critical 9.8)
- [CVE-2015-8360](https://insights.sbomify.com/CVE-2015-8360/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9514 and fix it if it is affected.

What it is: CVE-2017-9514 is a high-severity unsafe deserialization vulnerability in Atlassian Bamboo, published on 12 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9514 in the wild and no public exploit code.

Affected product: Atlassian Bamboo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9514/ (Markdown: https://insights.sbomify.com/CVE-2017-9514/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9514
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9514
- OSV: https://osv.dev/vulnerability/CVE-2017-9514

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9514/
Summaries are generated and may contain mistakes; the official description above is the record.