BambooApplication · Atlassian
CVE-2024-21687
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThis 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a File Inclusion vulnerability in Atlassian Bamboo Data Center and Server affecting versions 9.0.0 through 9.6.0. An authenticated attacker can leverage this flaw to read the contents of arbitrary local files on the server or execute locally stored files, leading to sensitive data exposure and potential remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
BambooApplication
>= 9.0.0, <= 9.0.4>= 9.1.0, <= 9.1.3>= 9.2.0, < 9.2.16>= 9.3.0, <= 9.3.6>= 9.4.0, <= 9.4.3>= 9.5.0, <= 9.5.4>= 9.6.0, < 9.6.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Atlassian Bamboo installationLook for Bamboo installation directories (commonly at /opt/atlassian/bamboo, /usr/local/bamboo, or C:\atlassian\bamboo on Windows). Check running processes for bamboo. Look for port 8085 (default Bamboo port) in netstat or similar network tools.Affected if Bamboo is installed and running on the system
-
Determine installed Bamboo versionCheck the version by logging into Bamboo as admin and navigating to About in the cog menu, or check the VERSION file in the installation directory, or look at the logs (atlassian-bamboo.log) which typically prints the version at startup.Affected if The version falls within any of these ranges: 9.0.0-9.0.4, 9.1.0-9.1.3, 9.2.0-9.2.15, 9.3.0-9.3.6, 9.4.0-9.4.3, 9.5.0-9.5.4, or 9.6.0-9.6.3
-
Verify authentication is required for file inclusion endpointsReview Bamboo's security configuration and examine which endpoints require authentication. Check if unauthenticated or low-privilege users can access file import/include functionality.Affected if The file inclusion endpoint is accessible to authenticated users with limited privileges, allowing them to manipulate file paths
-
Check for file import or template featuresLook for file import, file include, or template features in Bamboo's UI (typically under administration, repository, or plan configuration). These features may accept file paths or URLs as parameters.Affected if File import or include features are available that accept user-supplied paths without proper validation
You are affected if Atlassian Bamboo is running a version between 9.0.0 and 9.6.3 (inclusive) and an authenticated user can access file inclusion functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.2.169.6.4
Upgrade Bamboo to the latest version or to one of the specified supported fixed versions as listed in the release notes.
Latest available Bamboo version (at minimum: 9.2.16 or later for 9.2.x branch, 9.4.0+ for 9.3.x and earlier branches)
- 1. Back up your Bamboo Data Center or Server instance and database before proceeding with any upgrade.
- 2. Review the Bamboo release notes at https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html to identify the latest compatible version for your deployment.
- 3. Download the latest Bamboo version from https://www.atlassian.com/software/bamboo/download-archives.
- 4. Follow Atlassian's standard upgrade documentation for Bamboo Data Center/Server to apply the upgrade.
- 5. After upgrade, verify the vulnerability is remediated by confirming the file inclusion vector is no longer accessible to authenticated users.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Bamboo
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21687 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21687 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data