dbcve.org
Confluence Data CenterApplication · Atlassian

CVE-2023-22512

HIGH · 7.5 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 7.19.14 / 8.5.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 DoS (Denial of Service) vulnerability was introduced in version 5.6.0 of Confluence Data Center and Server. With a CVSS Score of 7.5, this vulnerability allows an unauthenticated attacker to cause a resource to be unavailable for its intended users by temporarily or indefinitely disrupting services of a vulnerable host (Confluence instance) connected to a network, which has no impact to confidentiality, no 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: Confluence Data Center and Server 7.19: Upgrade to a release greater than or equal to 7.19.14 Confluence Data Center and Server 8.5: Upgrade to a release greater than or equal to 8.5.1 Confluence Data Center and Server 8.6 or above: No need to upgrade, you're already on a patched version 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 confidence

This is a Denial of Service (DoS) vulnerability in Atlassian Confluence Data Center and Server introduced in version 5.6.0. An unauthenticated remote attacker can exploit this flaw to make Confluence resources unavailable to legitimate users, impacting availability without affecting confidentiality or integrity.

MitigationUpgrade Confluence to a supported fixed version: 7.19.14 or higher, 8.5.1 or higher, or 8.6 and above.

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:>= 5.6, < 7.19.14>= 8.0.0, < 8.5.1
Confluence ServerApplication
Affected:>= 5.6, < 7.19.14>= 8.0.0, < 8.5.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Log in as an administrator and navigate to the Confluence Administration > About page, or check the confluence-version.properties file in the Confluence home directory
    Affected if The displayed version falls within the ranges 5.6 to 7.19.13, or 8.0.0 to 8.5.0
  2. Verify Confluence deployment type
    Confirm whether the installation is Confluence Data Center or Confluence Server. This is typically visible in the administration console footer or the about page
    Affected if The deployment is Data Center or Server and the version meets the condition in step 1
  3. Confirm network exposure
    Verify that the Confluence instance is accessible over the network to unauthenticated users. Check if the /public/ or /wiki/ endpoints are exposed without authentication requirements
    Affected if The instance accepts unauthenticated requests from remote sources (this is the exploitation vector for the vulnerability)

An environment is affected if it runs Confluence Data Center or Server version 5.6 through 7.19.13, or version 8.0.0 through 8.5.0, and allows unauthenticated remote network access to the service.

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.14 / 8.5.1 or later
Fixed in 7.19.148.5.1
Interim mitigation

Upgrade Confluence to a supported fixed version: 7.19.14 or higher, 8.5.1 or higher, or 8.6 and above.

Recommended fix High confidence

7.19.14+ (7.x line) or 8.5.1+ (8.x line)

  1. 1. Determine current Confluence version by checking the Confluence administration console or running confluence version check
  2. 2. Take a complete backup of the Confluence database and home directory before upgrading
  3. 3. For versions 7.x (>= 7.19.0 and < 7.19.14): Upgrade to Confluence 7.19.14 or later
  4. 4. For versions 8.0.0 - 8.5.0: Upgrade to Confluence 8.5.1 or later
  5. 5. For versions 8.6.0 and above: Already running a patched version, no upgrade needed
  6. 6. After upgrade, restart Confluence and verify services are operational
  7. 7. Confirm the vulnerability is resolved by reviewing Confluence release notes for the installed version
Caveat Standard Confluence upgrade precautions apply - review release notes for breaking changes between major versions before upgrading

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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