Confluence Data CenterApplication · Atlassian

CVE-2024-21674

HIGH · 7.5 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 →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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 ).

Technical summary

dbcve analysis · high confidence

An unauthenticated Remote Code Execution vulnerability in Confluence Data Center and Server allows remote attackers to execute arbitrary code via network access. The vulnerability was introduced in version 7.13.0 and affects Confluence instances with high confidentiality impact but no integrity or availability impact.

MitigationUpgrade Confluence Data Center and Server to a supported fixed version (7.19.18+, 8.5.5+, or 8.7.2+) as specified in Atlassian's advisory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

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

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Confluence version

Access the About page at /about/ (e.g., https://your-confluence-instance/about/) or check the installation directory for the version file. Administrators can also view version via Administration > General Configuration > Confluence Admin > About Confluence.

Affected if The installed 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.2 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.
Verify Confluence is network-accessible

Confirm the Confluence web interface is reachable from network locations. This is typically the default configuration for most installations. Test by accessing the base URL from an external host or review reverse proxy/load balancer configurations.

Affected if The Confluence portal is exposed to network access (unauthenticated), which is required for the unauthenticated RCE to be exploitable.
Confirm installation type

Identify whether the installation is Confluence Data Center or Confluence Server. Check the UI footer, about page, or installation documentation. Data Center typically shows 'Data Center' in licensing, while Server shows 'Server'.

Affected if The installation is Confluence Data Center or Server version 7.19.x before 7.19.18, 8.5.x before 8.5.5, or 8.7.x at or below 8.7.2.

You are affected if your Confluence Data Center or Server version is 7.19.0-7.19.17, 8.5.0-8.5.4, or 8.7.0-8.7.2 AND the instance is accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Remediation

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 a supported fixed version (7.19.18+, 8.5.5+, or 8.7.2+) as specified in Atlassian's advisory.

Recommended fix High confidence

7.19.18, 8.5.5, or 8.7.2 (or respective higher x.x versions)

Back up your Confluence database and home directory before upgrading
Download the appropriate fixed version from Atlassian's download center: 7.19.18 (or higher 7.19.x), 8.5.5 (or higher 8.5.x), or 8.7.2 (or higher 8.7.x
Stop the Confluence service
Follow Atlassian's standard upgrade procedure for Confluence Data Center or Server
After upgrade, restart Confluence and verify the instance is operational
Review the Confluence release notes for any known post-upgrade considerations

Caveat Review Confluence release notes for the target version to check for any breaking changes or required 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
Implementation8.0 h
Testing6.0 h
Review / QA2.0 h

20.0 hours of engineering $3,500

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

confluence.atlassian.comVendor Advisory
jira.atlassian.comPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21674 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-21674?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 7.19.18 / 8.5.5 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 1.8%

Affects: Confluence Data Center

Remediation

A high-priority fix

Fix this in Confluence Data Center 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-21674 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References