# CVE-2023-22508: Code injection in Confluence Data Center > Authenticated attackers can execute arbitrary code on Confluence Data Center and Server instances, 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:** 18 Jul 2023 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-jq45-hqc5-f722 ## What is CVE-2023-22508? CVE-2023-22508 is a high-severity code injection vulnerability in Atlassian Confluence Data Center, published on 18 Jul 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 known as CVE-2023-22508 was introduced in version 6.1.0 of Confluence Data Center & 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 no user interaction. Atlassian recommends that you upgrade your instance to avoid this bug using the following options: * Upgrade to a Confluence feature release greater than or equal to 8.2.0 (ie: 8.2, 8.2, 8.4, etc...) * Upgrade to a Confluence 7.19 LTS bugfix release greater than or equal to 7.19.8 (ie: 7.19.8, 7.19.9, 7.19.10, 7.19.11, etc...) * Upgrade to a Confluence 7.13 LTS bugfix release greater than or equal to 7.13.20 (Release available early August) See the release notes (https://confluence.atlassian.com/doc/confluence-release-notes-327.html ). You can download the latest version of Data Center & Server from the download center (https://www.atlassian.com/software/confluence/download-archives ). If you are unable to upgrade your instance please use the following guide to workaround the issue https://confluence.atlassian.com/confkb/how-to-disable-the-jmx-network-port-for-cve-2023-22508-1267761550.html This vulnerability was discovered by a private user and reported via our Bug Bounty program. ## Which versions are affected by CVE-2023-22508? It affects 2 products. Products: Atlassian Confluence Data Center, Atlassian Confluence Server. ## How do I fix CVE-2023-22508? No fix has been published for CVE-2023-22508 yet. Limit exposure of the affected software until one is available. ## Is CVE-2023-22508 being exploited? There is no known exploitation of CVE-2023-22508 in the wild and no public exploit code. ## Other vulnerabilities in Atlassian Confluence Data Center - [CVE-2023-22527](https://insights.sbomify.com/CVE-2023-22527/): Atlassian Confluence Data Center and Server Template Injection (critical 10.0, exploited in the wild) - [CVE-2023-22518](https://insights.sbomify.com/CVE-2023-22518/): Atlassian Confluence Data Center and Server Improper Authorization (critical 10.0, exploited in the wild) - [CVE-2023-22515](https://insights.sbomify.com/CVE-2023-22515/): Atlassian Confluence Data Center and Server Broken Access Control (critical 10.0, exploited in the wild) - [CVE-2022-26134](https://insights.sbomify.com/CVE-2022-26134/): Atlassian Confluence Server and Data Center Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2021-26084](https://insights.sbomify.com/CVE-2021-26084/): Atlassian Confluence Server and Data Center Object-Graph Navigation Language (OGNL) Injection (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-22508 and fix it if it is affected. What it is: CVE-2023-22508 is a high-severity code injection vulnerability in Atlassian Confluence Data Center, published on 18 Jul 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-22508 in the wild and no public exploit code. Affected product: Atlassian Confluence 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-22508/ (Markdown: https://insights.sbomify.com/CVE-2023-22508/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22508 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22508 - OSV: https://osv.dev/vulnerability/CVE-2023-22508 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-22508/ Summaries are generated and may contain mistakes; the official description above is the record.