dbcve.org
Confluence Data CenterApplication · Atlassian

CVE-2024-21672

HIGH · 8.8 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 7.19.18 / 8.5.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Remote Code Execution (RCE) vulnerability was introduced in version 2.1.0 of Confluence Data Center and Server. Remote Code Execution (RCE) vulnerability, with a CVSS Score of 8.3 and a CVSS Vector of CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H allows an unauthenticated attacker to remotely expose assets in your environment susceptible to exploitation which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires 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).

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 · moderate confidence

This is a Remote Code Execution (RCE) vulnerability in Atlassian Confluence Data Center and Server that allows an unauthenticated attacker to execute arbitrary code remotely. The vulnerability was introduced in version 2.1.0 of a component and is exploitable via network attack (AV:N) with user interaction required.

MitigationUpgrade Confluence Data Center or Server to one of the supported fixed versions: 7.19.18+, 8.5.5+, or 8.7.2+ to remediate this vulnerability.

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
Confluence Data CenterApplication
Affected:>= 7.19.0, < 7.19.18>= 8.5.0, < 8.5.5>= 8.7.0, < 8.7.2
Confluence ServerApplication
Affected:>= 7.19, < 7.19.18>= 8.5.0, < 8.5.5>= 8.7.0, <= 8.7.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify Confluence installation version
    Access the Confluence administration console or check the confluence-version file typically found in the Confluence installation directory. Alternatively, access the /about endpoint or check the footer of any Confluence page which often displays the version number.
    Affected if The displayed version falls within these ranges: 7.19.0 through 7.19.17, 8.5.0 through 8.5.4, or 8.7.0 through 8.7.1 (for Data Center); or 7.19.0 through 7.19.17, 8.5.0 through 8.5.4, or 8.7.0 through 8.7.2 (for Server).
  2. Confirm Confluence edition type
    Check whether the installation is Confluence Data Center or Confluence Server. This is typically visible in the administration console header, the license information, or the /about page.
    Affected if The edition is Data Center or Server and the version matches the affected ranges listed in step 1.
  3. Verify network exposure
    Determine if the Confluence instance is directly accessible from the network (not behind a properly configured firewall or VPN). This vulnerability is exploitable remotely (AV:N), so external network accessibility increases risk.
    Affected if Confluence is accessible from untrusted networks and the installed version falls within affected version ranges.
  4. Check user interaction likelihood
    Assess whether typical Confluence users would encounter content that could trigger the vulnerability. This includes viewing or interacting with user-submitted content, attachments, or macros.
    Affected if Users regularly interact with content from other users or external sources and the version is affected.

A user is affected if their Confluence Data Center or Server version is 7.19.x below 7.19.18, 8.5.x below 8.5.5, or 8.7.x below 8.7.2 (for Data Center) or up to 8.7.2 (for Server), and the instance is network-accessible with user interaction possible.

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 7.19.18 / 8.5.5 / 8.7.2 or later
Fixed in 7.19.188.5.58.7.2
Interim mitigation

Upgrade Confluence Data Center or Server to one of the supported fixed versions: 7.19.18+, 8.5.5+, or 8.7.2+ to remediate this vulnerability.

Recommended fix High confidence

7.19.18 (or later 7.19.x) / 8.5.5 (or later 8.5.x) / 8.7.2 (or later) depending on your current branch

  1. 1. Take a complete backup of your Confluence database and home directory
  2. 2. Review the Confluence upgrade guide and release notes for your target version
  3. 3. Download the appropriate fixed version (7.19.18, 8.5.5, or 8.7.2 or later) from the Atlassian download center
  4. 4. Stop the Confluence service
  5. 5. Run the installer for the chosen fixed version, following standard upgrade procedures
  6. 6. Start the Confluence service after upgrade completes
  7. 7. Verify the instance is functioning correctly and the vulnerability is resolved
Caveat Review release notes for potential configuration or compatibility changes between your current version and target version

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

Fix this in Confluence 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-2024-21672 — 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-2024-21672 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