dbcve.org
Confluence Data CenterApplication · Atlassian

CVE-2024-21683

HIGH · 8.8 CVSS v3.1 Published 2024-05-21
Fix available
A fix is available. Upgrade to 4.8.15 / 5.4.21 or later.
See remediation →
94/100
Remediation priority · Urgent
High EPSS 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 RCE (Remote Code Execution) vulnerability was introduced in version 5.2 of Confluence Data Center and Server. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 7.2, 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 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. 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. This vulnerability was found internally.

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 an authenticated Remote Code Execution (RCE) vulnerability affecting Confluence Data Center and Server starting from version 5.2. An authenticated attacker can execute arbitrary code on the affected system with high impact to confidentiality, integrity, and availability, requiring no user interaction.

MitigationUpgrade Confluence Data Center and Server to the latest version or one of the specified supported fixed versions referenced in the Atlassian release notes.

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.24>= 7.20.0, <= 7.20.3>= 8.0.0, <= 8.0.4>= 8.1.0, <= 8.1.4>= 8.2.0, <= 8.2.3>= 8.3.0, <= 8.3.4>= 8.4.0, <= 8.4.5>= 8.5.0, < 8.5.11>= 8.6.0, <= 8.6.2>= 8.9.0, < 8.9.3= 8.7.1= 8.7.2
Confluence ServerApplication
Affected:>= 7.19.0, < 7.19.24>= 7.20.0, <= 7.20.3>= 8.0.0, <= 8.0.4>= 8.1.0, <= 8.1.4>= 8.2.0, <= 8.2.3>= 8.3.0, <= 8.3.4>= 8.4.0, <= 8.4.5>= 8.5.0, < 8.5.11>= 8.6.0, <= 8.6.2>= 8.9.0, <= 8.9.2= 8.7.1= 8.7.2
FisheyeApplication
Affected:>= 4.8.0, < 4.8.15
CrucibleApplication
Affected:>= 4.8.0, < 4.8.15
Jira Data CenterApplication
Affected:>= 9.4.0, < 9.4.21>= 9.12.0, < 9.12.8
Jira ServerApplication
Affected:>= 9.4.0, < 9.4.21>= 9.12.0, < 9.12.8
Jira Service ManagementApplication
Affected:>= 5.4.0, < 5.4.21>= 5.12.0, < 5.12.8>= 5.15.2, < 5.16.0= 5.15.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 the installed Atlassian product
    Inspect the application banner, process name, or installation directory to determine if the system is running Confluence, Fisheye, Crucible, or Jira (including Jira Service Management)
    Affected if The product matches one of the affected products listed in the CVE (Confluence Data Center/Server, Fisheye, Crucible, Jira Data Center/Server, Jira Service Management)
  2. Determine the installed version of the Atlassian product
    Locate the version file or configuration in the product installation directory (typically VERSION.txt, version.properties, or the admin UI about page)
    Affected if The installed version falls within any of the affected version ranges: Confluence 7.19.0 to <7.19.24, 7.20.0 to 7.20.3, 8.0.0 to 8.0.4, 8.1.0 to 8.1.4, 8.2.0 to 8.2.3, 8.3.0 to 8.3.4, 8.4.0 to 8.4.5, 8.5.0 to <8.5.11, 8.6.0 to 8.6.2, 8.7.1, 8.7.2, 8.9.0 to <8.9.3; Fisheye/Crucible 4.8.0 to <4.8.15;
  3. Verify if user authentication is enabled
    Check the product configuration for user authentication settings (typically in confluence.cfg.xml for Confluence or the general configuration for Jira)
    Affected if Authentication is enabled (the vulnerability requires an authenticated attacker, so unauthenticated exposure alone does not guarantee exploitation but combined with authentication being enabled creates the condition for exploitability)

The environment is affected if it runs any of the listed Atlassian products (Confluence, Fisheye, Crucible, Jira, or Jira Service Management) at a version within the specified vulnerable ranges and has authentication enabled, allowing an authenticated attacker to achieve RCE.

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 4.8.15 / 5.4.21 / 5.12.8 or later
Fixed in 4.8.155.4.215.12.8
Interim mitigation

Upgrade Confluence Data Center and Server to the latest version or one of the specified supported fixed versions referenced in the Atlassian release notes.

Recommended fix High confidence

Latest Confluence 8.x (8.5.0+), Jira 9.12.x (9.12.8+), Jira Service Management 5.16.x, Fisheye/Crucible 4.8.15+

  1. Identify your current Confluence, Fisheye, Crucible, Jira, or Jira Service Management version
  2. Determine which affected product and version range your instance falls into
  3. Back up your data and configuration before upgrading
  4. For Confluence Data Center/Server: upgrade to version 7.19.24 or later, 7.21.0 or later, 8.0.5 or later, 8.1.5 or later, or the latest available version
  5. For Fisheye/Crucible: upgrade to version 4.8.15 or later
  6. For Jira Data Center/Server: upgrade to version 9.4.21 or later, 9.12.8 or later, or the latest available version
  7. For Jira Service Management: upgrade to version 5.4.21 or later, 5.12.8 or later, 5.16.0 or later, or the latest available version
  8. After upgrade, verify the instance is running and accessible
Caveat Review Atlassian release notes for potential breaking changes between versions; some upgrades may require migration steps

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

Fix this in Confluence Data Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21683 — 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-21683 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