# CVE-2024-21674: Code injection in Confluence Data Center > Unauthenticated attackers can execute arbitrary code and expose sensitive assets in Confluence Data Center and Server environments. - **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 16 Jan 2024 - **Updated:** 29 Aug 2024 - **Also known as:** GHSA-p3fj-jhx6-26mr ## What is CVE-2024-21674? CVE-2024-21674 is a high-severity code injection vulnerability in Atlassian Confluence Data Center, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description This High severity Remote Code Execution (RCE) vulnerability was introduced in version 7.13.0 of Confluence Data Center and Server. Remote Code Execution (RCE) vulnerability, with a CVSS Score of 8.6 and a CVSS Vector of CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation which has high impact to confidentiality, no impact to integrity, no impact to availability, and does not require user interaction. Atlassian recommends that Confluence 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: * Confluence Data Center and Server 7.19: Upgrade to a release 7.19.18, or any higher 7.19.x release * Confluence Data Center and Server 8.5: Upgrade to a release 8.5.5 or any higher 8.5.x release * Confluence Data Center and Server 8.7: Upgrade to a release 8.7.2 or any higher release See the release notes (https://confluence.atlassian.com/doc/confluence-release-notes-327.html ). You can download the latest version of Confluence Data Center and Server from the download center (https://www.atlassian.com/software/confluence/download-archives ). Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2024-21674? It affects 2 products. Products: Atlassian Confluence Data Center, Atlassian Confluence Server. ## How do I fix CVE-2024-21674? No fix has been published for CVE-2024-21674 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-21674 being exploited? There is no known exploitation of CVE-2024-21674 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-2024-21674 and fix it if it is affected. What it is: CVE-2024-21674 is a high-severity code injection vulnerability in Atlassian Confluence Data Center, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-21674 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-2024-21674/ (Markdown: https://insights.sbomify.com/CVE-2024-21674/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-21674 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-21674 - OSV: https://osv.dev/vulnerability/CVE-2024-21674 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-21674/ Summaries are generated and may contain mistakes; the official description above is the record.