All versions of Confluence Data Center and Server are affected by this unexploited vulnerability.
All Confluence Data Center and Server versions are affected, and no fixed version is listed in the checked facts. Blocking the setup-restore endpoints is the listed workaround.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Atlassian Confluence Data Center and Server installations are affected, but Atlassian-hosted Cloud sites are not. An unauthenticated attacker could exploit this flaw to reset the instance and create an administrator account, gaining full control over the data and availability of the affected Confluence system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
All versions of Confluence Data Center and Server are affected by this unexploited vulnerability. This Improper Authorization vulnerability allows an unauthenticated attacker to reset Confluence and create a Confluence instance administrator account. Using this account, an attacker can then perform all administrative actions that are available to Confluence instance administrator leading to - but not limited to - full loss of confidentiality, integrity and availability. Atlassian Cloud sites are not affected by this vulnerability. If your Confluence site is accessed via an atlassian.net domain, it is hosted by Atlassian and is not vulnerable to this issue.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Atlassian Confluence Data Center
From 1.0.0
- Atlassian Confluence Server
From 1.0.0
References 3
confluence.atlassian.com
jira.atlassian.com
packetstormsecurity.com
Questions about CVE-2023-22518
What does this mean?
Without logging in, a person can reset Confluence and create an instance administrator account. With that account they can perform all administrative actions, which means full loss of confidentiality, integrity and availability.Source: confluence.atlassian.com
Am I affected, and how do I check?
The checked facts list Confluence Data Center and Confluence Server, all versions from 1.0.0 onward. Compare your installation's product and version against this list.Source: confluence.atlassian.com
What should I do about it?
The checked facts name no fixed version, so no upgrade target can be given here. Apply the workaround now and check Atlassian's advisory for a fixed release.Source: confluence.atlassian.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-11-07, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data
What if there's no patch?
Block access to the /json/setup-restore.action, /json/setup-restore-local.action and /json/setup-restore-progress.action endpoints, either at the network layer or in web.xml.Source: confluence.atlassian.com