# CVE-2023-22513: Code injection in Bitbucket Data Center > An authenticated attacker can execute arbitrary code on Bitbucket Data Center and Server, compromising confidentiality, integrity, and availability. - **Severity:** High 8.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **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:** 19 Sep 2023 - **Updated:** 6 Mar 2025 - **Also known as:** GHSA-3f2j-57ff-r6p5 ## What is CVE-2023-22513? CVE-2023-22513 is a high-severity code injection vulnerability in Atlassian Bitbucket Data Center, published on 19 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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 Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2023-22513? It affects 2 products. Products: Atlassian Bitbucket Data Center, Atlassian Bitbucket Server. ## How do I fix CVE-2023-22513? No fix has been published for CVE-2023-22513 yet. Limit exposure of the affected software until one is available. ## Is CVE-2023-22513 being exploited? There is no known exploitation of CVE-2023-22513 in the wild and no public exploit code. ## Other vulnerabilities in Atlassian Bitbucket Data Center - [CVE-2022-26133](https://insights.sbomify.com/CVE-2022-26133/): Deserialization in Bitbucket Data Center (critical 9.8) - [CVE-2024-21684](https://insights.sbomify.com/CVE-2024-21684/): Open redirect in Bitbucket Data Center (low 3.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-22513 and fix it if it is affected. What it is: CVE-2023-22513 is a high-severity code injection vulnerability in Atlassian Bitbucket Data Center, published on 19 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-22513 in the wild and no public exploit code. Affected product: Atlassian Bitbucket 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-2023-22513/ (Markdown: https://insights.sbomify.com/CVE-2023-22513/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22513 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22513 - OSV: https://osv.dev/vulnerability/CVE-2023-22513 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-22513/ Summaries are generated and may contain mistakes; the official description above is the record.