dbcve.org
Bitbucket Data CenterApplication · Atlassian

CVE-2023-22513

HIGH · 8.8 CVSS v3.1 Published 2023-09-19
Fix available
A fix is available. Upgrade to 8.9.5 / 8.10.5 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 version 8.0.0 of Bitbucket 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 Bitbucket 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: Bitbucket Data Center and Server 8.9: Upgrade to a release greater than or equal to 8.9.5 Bitbucket Data Center and Server 8.10: Upgrade to a release greater than or equal to 8.10.5 Bitbucket Data Center and Server 8.11: Upgrade to a release greater than or equal to 8.11.4 Bitbucket Data Center and Server 8.12: Upgrade to a release greater than or equal to 8.12.2 Bitbucket Data Center and Server 8.13: Upgrade to a release greater than or equal to 8.13.1 Bitbucket Data Center and Server 8.14: Upgrade to a release greater than or equal to 8.14.0 Bitbucket Data Center and Server version >= 8.0 and < 8.9: Upgrade to any of the listed fix versions. See the release notes (https://confluence.atlassian.com/bitbucketserver/release-notes). You can download the latest version of Bitbucket Data Center and Server from the download center (https://www.atlassian.com/software/bitbucket/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 RCE vulnerability in Atlassian Bitbucket Data Center and Server affecting versions 8.0.0 through the versions prior to the fixed releases. An authenticated attacker can execute arbitrary code on the affected system with high impact to confidentiality, integrity, and availability, requiring no user interaction.

MitigationUpgrade Bitbucket Data Center or Server to one of the supported fixed versions (8.9.5+, 8.10.5+, 8.11.4+, 8.12.2+, 8.13.1+, or 8.14.0+) as specified in the official advisory.

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
Bitbucket Data CenterApplication
Affected:>= 8.9.0, < 8.9.5>= 8.10.0, < 8.10.5>= 8.11.0, < 8.11.4>= 8.12.0, < 8.12.2= 8.13.0
Bitbucket ServerApplication
Affected:>= 8.9.0, < 8.9.5>= 8.10.0, < 8.10.5>= 8.11.0, < 8.11.4>= 8.12.0, < 8.12.2= 8.13.0

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. Check Bitbucket version from the web UI
    Log into Bitbucket and look at the footer of any page - the version is displayed there. Alternatively, go to the administration area and navigate to 'About' or 'Application' to see the full version number.
    Affected if The displayed version falls within these ranges: 8.9.0-8.9.4, 8.10.0-8.10.4, 8.11.0-8.11.3, 8.12.0-8.12.1, or exactly 8.13.0
  2. Check Bitbucket version via REST API
    Make an authenticated GET request to /rest/api/1.0/application-properties and look for the 'version' field in the JSON response.
    Affected if The version field value matches the affected ranges listed above
  3. Verify the product edition (Data Center or Server)
    In the Bitbucket administration area, look for the product type indicator - it will show either 'Bitbucket Data Center' or 'Bitbucket Server'. This is also visible in the 'About' page.
    Affected if The product is either Bitbucket Data Center or Bitbucket Server and the version is in the affected ranges

You are affected if your Bitbucket Data Center or Server installation is running version 8.9.0 through 8.9.4, 8.10.0 through 8.10.4, 8.11.0 through 8.11.3, 8.12.0 through 8.12.1, or exactly version 8.13.0.

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 8.9.5 / 8.10.5 / 8.11.4 or later
Fixed in 8.9.58.10.58.11.4
Interim mitigation

Upgrade Bitbucket Data Center or Server to one of the supported fixed versions (8.9.5+, 8.10.5+, 8.11.4+, 8.12.2+, 8.13.1+, or 8.14.0+) as specified in the official advisory.

Recommended fix High confidence

8.14.0 (or latest stable release)

  1. 1. Back up your Bitbucket Data Center/Server instance database and configuration files
  2. 2. Review the Bitbucket upgrade guide at https://confluence.atlassian.com/bitbucketserver/upgrade-bitbucket-server-1104374559.html
  3. 3. Download the desired fixed version from https://www.atlassian.com/software/bitbucket/download-archives
  4. 4. Stop the Bitbucket service
  5. 5. Install the upgraded version following standard Bitbucket upgrade procedures
  6. 6. Start the Bitbucket service and verify the application is functioning correctly
  7. 7. Confirm the upgrade was successful by checking the version in the Bitbucket administration console
Caveat Standard Bitbucket upgrade considerations apply - review release notes for your target version for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bitbucket Data Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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