dbcve.org
BambooApplication · Atlassian

CVE-2023-22516

HIGH · 8.8 CVSS v3.1 Published 2023-11-21
Fix available
A fix is available. Upgrade to 9.2.7 / 9.3.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 was introduced in versions 8.1.0, 8.2.0, 9.0.0, 9.1.0, 9.2.0, and 9.3.0 of Bamboo Data Center and Server. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 8.5, allows an authenticated attacker to execute arbitrary code which has high impact to confidentiality, high impact to integrity, high 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: Bamboo Data Center and Server 9.2: Upgrade to a release greater than or equal to 9.2.7. JDK 1.8u121+ should be used in case Java 8 used to run Bamboo Data Center and Server. See Bamboo 9.2 Upgrade notes (https://confluence.atlassian.com/bambooreleases/bamboo-9-2-upgrade-notes-1207179212.html) Bamboo Data Center and Server 9.3: Upgrade to a release greater than or equal to 9.3.4 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 discovered by a private user and 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

This is an authenticated Remote Code Execution (RCE) vulnerability in Atlassian Bamboo Data Center and Server. An authenticated attacker can execute arbitrary code on the affected system with high impact to confidentiality, integrity, and availability, requiring no user interaction.

MitigationUpgrade Bamboo to version 9.2.7 or later (for 9.2.x branches) or 9.3.4 or later (for 9.3.x branches). For environments using Java 8, ensure JDK 1.8u121 or later is used.

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:>= 8.1.0, < 9.2.7>= 9.3.0, < 9.3.4

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Locate Bamboo installation directory
    Check common installation paths such as /opt/atlassian/bamboo or look for the bamboo-web application. Alternatively, access the Bamboo web interface and navigate to All > Administration > Overview to find the installation path.
    Affected if Bamboo is installed on the system
  2. Determine installed Bamboo version
    Check the version file in the Bamboo installation directory, or log into the Bamboo web interface and go to All > Administration > Overview to view the version number displayed under 'Bamboo version'.
    Affected if Version number cannot be determined or is not visible
  3. Compare version against affected ranges
    Verify the installed version against the affected ranges: version >= 8.1.0 AND < 9.2.7, OR version >= 9.3.0 AND < 9.3.4. If the version falls into any of these ranges, the instance is vulnerable.
    Affected if Installed version matches >= 8.1.0 and < 9.2.7, or >= 9.3.0 and < 9.3.4
  4. Verify authentication is required for the instance
    Confirm whether the Bamboo instance requires user authentication. Check if anonymous access is enabled by reviewing the Bamboo security configuration or by attempting to access restricted endpoints without credentials.
    Affected if Anonymous access is enabled or attacker can authenticate to the instance

The environment is affected if Bamboo is installed with a version in the range 8.1.0 to 9.2.6, or 9.3.0 to 9.3.3, and an attacker can authenticate to the instance.

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.7 / 9.3.4 or later
Fixed in 9.2.79.3.4
Interim mitigation

Upgrade Bamboo to version 9.2.7 or later (for 9.2.x branches) or 9.3.4 or later (for 9.3.x branches). For environments using Java 8, ensure JDK 1.8u121 or later is used.

Recommended fix High confidence

Bamboo 9.2.7 or later, or Bamboo 9.3.4 or later (depending on your current major version)

  1. 1. Identify your current Bamboo version by checking the Bamboo administration console or running 'bamboo --version'
  2. 2. Determine your upgrade path: if on 8.x, upgrade first to 9.2.7+; if on 9.0.x-9.2.x, upgrade to 9.2.7+; if on 9.3.x, upgrade to 9.3.4+
  3. 3. Perform a full backup of your Bamboo instance including database and home directory
  4. 4. Review the Bamboo 9.2 Upgrade notes at confluence.atlassian.com/bambooreleases/bamboo-9-2-upgrade-notes-1207179212.html for version-specific considerations
  5. 5. If running Java 8, ensure JDK is version 1.8u121 or later before upgrading
  6. 6. Download the target fixed version from atlassian.com/software/bamboo/download-archives
  7. 7. Stop the Bamboo service
  8. 8. Follow Atlassian's standard Bamboo upgrade procedure (install new version over existing, preserving configuration)
Caveat Review Bamboo 9.2 upgrade notes for potential configuration or compatibility considerations 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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22516 — 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-2023-22516 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