# CVE-2024-21687: File upload in Bamboo Data Center

> Authenticated attackers can read local files or execute stored files in Atlassian Bamboo, compromising confidentiality and integrity.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 16 Jul 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-87p8-wr2m-jhp2

## What is CVE-2024-21687?

CVE-2024-21687 is a high-severity vulnerability in Atlassian Bamboo Data Center, published on 16 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This High severity File Inclusion vulnerability was introduced in versions 9.0.0, 9.1.0, 9.2.0, 9.3.0, 9.4.0, 9.5.0 and 9.6.0 of Bamboo Data Center and Server.

This File Inclusion vulnerability, with a CVSS Score of 8.1, allows an authenticated attacker to get the application to display the contents of a local file, or execute a different files already stored locally on the server which has high impact to confidentiality, high impact to integrity, no impact to availability, and requires no user interaction.

Atlassian recommends that Bamboo Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions listed on this CVE

See the release notes (https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html). You can download the latest version of Bamboo Data Center and Server from the download center (https://www.atlassian.com/software/bamboo/download-archives).

This vulnerability was reported via our Bug Bounty program.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2024-21687?

It affects 1 product.


Products: Atlassian Bamboo.

## How do I fix CVE-2024-21687?

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

## Is CVE-2024-21687 being exploited?

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

## Other vulnerabilities in Atlassian Bamboo Data Center

- [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-2024-21687 and fix it if it is affected.

What it is: CVE-2024-21687 is a high-severity vulnerability in Atlassian Bamboo Data Center, published on 16 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-21687 in the wild and no public exploit code.

Affected product: Atlassian Bamboo Data Center. 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-2024-21687/ (Markdown: https://insights.sbomify.com/CVE-2024-21687/index.md)
```

## Sources

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

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