dbcve.org
BambooApplication · Atlassian

CVE-2024-21689

HIGH · 8.0 CVSS v3.1 Published 2024-08-20
Fix available
A fix is available. Upgrade to 9.2.17 / 9.6.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 · unedited
This High severity RCE (Remote Code Execution) vulnerability CVE-2024-21689  was introduced in versions 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 RCE (Remote Code Execution) vulnerability, with a CVSS Score of 7.6, allows an authenticated attacker to execute arbitrary code which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires 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: Bamboo Data Center and Server 9.2: Upgrade to a release greater than or equal to 9.2.17 Bamboo Data Center and Server 9.6: Upgrade to a release greater than or equal to 9.6.5 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 confidence

CVE-2024-21689 is an authenticated remote code execution vulnerability in Atlassian Bamboo Data Center and Server affecting versions 9.1.0 through 9.6.0. An authenticated attacker can execute arbitrary code on the target system with high impact to confidentiality, integrity, and availability.

MitigationUpgrade Bamboo to version 9.2.17 or later (for 9.2.x branches) or version 9.6.5 or later (for 9.6.x branches). If immediate upgrade is not possible, apply compensating controls such as network segmentation and strict access controls for authenticated users.

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
Affected:>= 9.1.0, < 9.2.17>= 9.3.0, < 9.6.5

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Bamboo version in admin UI
    Log into the Bamboo administration console and navigate to 'About' or 'System Information' to view the installed version number
    Affected if The displayed version falls within 9.1.0 to 9.2.16, or 9.3.0 to 9.6.4
  2. Check version via HTTP endpoint
    Access the Bamboo base URL and append '/admin/systemInfo.action' or check the footer of any Bamboo page for the version display
    Affected if The version shown is >= 9.1.0 and < 9.2.17, or >= 9.3.0 and < 9.6.5
  3. Verify Bamboo component version from logs
    Examine the 'atlassian-bamboo.log' file in the Bamboo home directory for startup messages that display the version, or check the 'bamboo-version.txt' file in the installation directory
    Affected if The logged version matches the affected ranges listed above
  4. Confirm authentication is required
    Note that this vulnerability requires an authenticated user session; verify whether external user access is permitted and review user account security
    Affected if Bamboo is accessible to users who can authenticate, and the version is within the affected ranges

You are affected if your Bamboo Data Center or Server installation version is 9.1.0 through 9.2.16, or 9.3.0 through 9.6.4, and the instance allows authenticated user access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.2.17 / 9.6.5 or later
Fixed in 9.2.179.6.5
Interim mitigation

Upgrade Bamboo to version 9.2.17 or later (for 9.2.x branches) or version 9.6.5 or later (for 9.6.x branches). If immediate upgrade is not possible, apply compensating controls such as network segmentation and strict access controls for authenticated users.

Recommended fix High confidence

Bamboo 9.2: upgrade to >= 9.2.17; Bamboo 9.6: upgrade to >= 9.6.5; recommended: latest version (9.7.0 or higher)

  1. Back up your Bamboo Data Center or Server instance, including the database and home directory
  2. Review the Bamboo release notes for the target version to understand changes
  3. Download the fixed version (9.2.17, 9.6.5, or the latest version) from the Atlassian download center
  4. Stop the Bamboo service
  5. Install the upgrade following Atlassian's standard upgrade procedure
  6. Start the Bamboo service
  7. Verify the upgrade was successful by checking the Bamboo UI and testing key functionality
Caveat Review release notes for version-specific breaking changes before upgrading

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
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21689 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21689 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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