Confluence Data CenterApplication · Atlassian
CVE-2024-21677
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 · uneditedThis High severity Path Traversal vulnerability was introduced in version 6.13.0 of Confluence Data Center. This Path Traversal vulnerability, with a CVSS Score of 8.3, allows an unauthenticated attacker to exploit an undefinable vulnerability 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: Data Center Atlassian recommends that Confluence Data Center customers upgrade to the latest version and that Confluence Server customers upgrade to the latest 8.5.x LTS 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 reported via our Bug Bounty program.
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 confidencePath traversal vulnerability in Confluence Data Center and Server introduced in version 6.13.0, allowing unauthenticated attackers to access files outside intended directory boundaries via unspecified vectors, with high impact to confidentiality, integrity, and availability.
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
>= 6.13.0, < 7.19.20>= 7.20.0, < 8.5.7>= 8.6.0, < 8.8.1
Confluence ServerApplication
>= 6.13.0, < 7.19.20>= 7.20.0, < 8.5.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Confluence installation versionAccess the Confluence about page at /about.action or check the administration console under General Configuration > Confluence Administration > System Info. Alternatively, check the version file in the Confluence installation directory if you have file system access.Affected if The installed version falls within >= 6.13.0, < 7.19.20; >= 7.20.0, < 8.5.7; or >= 8.6.0, < 8.8.1 (for Data Center).
-
Determine Confluence edition (Data Center or Server)Check the Confluence administration console or license information to confirm whether you are running Data Center or Server edition, as version ranges differ slightly between them.Affected if Running Data Center or Server editions with versions in the affected ranges.
-
Verify Confluence is exposed to unauthenticated network accessConfirm whether the Confluence instance is accessible over the network without authentication. The vulnerability can be exploited by unauthenticated attackers, so check your firewall rules, Atlassian Crowd integration, and any authentication requirements configured in Confluence.Affected if Confluence is reachable from network without requiring authentication credentials.
Your Confluence instance is affected if it is running any Data Center or Server version from 6.13.0 up to but not including 7.19.20, or from 7.20.0 up to but not including 8.5.7 (Data Center also includes 8.6.0 to < 8.8.1), and is accessible to unauthenticated network users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.19.208.5.78.8.1
Upgrade Confluence Data Center to the latest version or Confluence Server to the latest 8.5.x LTS version to apply the vendor patch.
For Confluence Data Center: upgrade to latest version (8.8.1 or newer); For Confluence Server: upgrade to latest 8.5.x LTS version
- Backup your Confluence Data Center or Server instance before upgrading
- Review Atlassian's upgrade documentation for your specific version at confluence.atlassian.com
- Plan your upgrade path based on your current version: if on 6.13.x-7.19.x, upgrade to 7.19.20 or later; if on 7.20.x-8.5.x, upgrade to 8.5.7 or later; if on 8.6.x-8.8.0, upgrade to 8.8.1 or later
- Download the appropriate fixed version from https://www.atlassian.com/software/confluence/download-archives
- Stop the Confluence service
- Execute the upgrade following Atlassian's standard upgrade procedure
- Verify the upgrade was successful and the service starts correctly
- Confirm the vulnerability is remediated by testing the affected functionality
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
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21677 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21677 in production — separate from our analysis above.
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.
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.
- 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