dbcve.org
Confluence Data CenterApplication · Atlassian

CVE-2024-21673

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

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

An authenticated remote code execution vulnerability in Confluence Data Center and Server versions 7.13.0 and later allows attackers with high privileges to execute arbitrary code on the affected system via a network attack vector, without requiring user interaction.

MitigationUpgrade Confluence Data Center and Server to version 7.19.18 or higher, 8.5.5 or higher, or 8.7.2 or higher to remediate this RCE 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
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. Identify Confluence version via admin UI
    Log in as an administrator and navigate to Settings > General Configuration > About Confluence, or access /aboutconfluence page directly to view the installed version number.
    Affected if The displayed version falls within 7.19.0 to 7.19.17, 8.5.0 to 8.5.4, or 8.7.0 to 8.7.1.
  2. Confirm Confluence edition type
    Check the same About page or the administration console to verify the installation is Confluence Data Center or Confluence Server, not Confluence Cloud.
    Affected if The product shows Data Center or Server edition.
  3. Verify version from configuration file
    Locate the confluence.cfg.xml file in the <confluence-home>/ directory and search for the <buildNumber> or <version> element to confirm the exact installed version.
    Affected if The version number in the configuration file matches the affected ranges listed in the CVE.
  4. Check for network exposure
    Determine if the Confluence web interface is accessible from untrusted networks by reviewing firewall rules, load balancer configurations, or network ACLs restricting access to the HTTP port (default 8090).
    Affected if Confluence is reachable from the internet or untrusted networks without VPN or proper access controls.

You are affected if your Confluence Data Center or Server installation version is 7.19.0 through 7.19.17, 8.5.0 through 8.5.4, or 8.7.0 through 8.7.1, and the instance is network-accessible to attackers who could obtain high-privilege credentials.

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 and Server to version 7.19.18 or higher, 8.5.5 or higher, or 8.7.2 or higher to remediate this RCE vulnerability.

Recommended fix High confidence

Confluence Data Center/Server 7.19.18+ or 8.5.5+ or 8.7.2+ (latest respective release)

  1. 1. Identify your current Confluence version (Data Center or Server) by checking the Confluence administration console or using the /about endpoint
  2. 2. For Confluence 7.19.x: Upgrade to version 7.19.18 or later (recommended: latest 7.19.x release)
  3. 3. For Confluence 8.5.x: Upgrade to version 8.5.5 or later (recommended: latest 8.5.x release)
  4. 4. For Confluence 8.7.x: Upgrade to version 8.7.2 or later (recommended: latest 8.7.x release)
  5. 5. Download the appropriate version from the Atlassian download center: https://www.atlassian.com/software/confluence/download-archives
  6. 6. Review Confluence upgrade guides and release notes before upgrading: https://confluence.atlassian.com/doc/confluence-release-notes-327.html
  7. 7. Perform a full backup of your Confluence database and home directory before upgrading
  8. 8. Execute the upgrade following Atlassian's standard upgrade procedure for your deployment type
Caveat Review release notes for any configuration or compatibility changes between your current version and target version; ensure database and app compatibility

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-21673 — 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-21673 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