CVE-2023-22515 remediation guide
Atlassian Confluence Data Center and Server
Atlassian has been made aware of an issue reported by a handful of customers where external attackers may have exploited a previously unknown vulnerability in publicly accessible Confluence Data Center and Server instances to create unauthorized Confluence administrator accounts and access Confluence instances. 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.
Identify the affected asset
Confirm whether Atlassian Confluence Data Center and Server is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 8.0.0, >= 8.0.1, >= 8.0.2, >= 8.0.3, >= 8.1.3, >= 8.1.4, >= 8.2.0, >= 8.2.1, >= 8.2.2, >= 8.2.3, >= 8.3.0, >= 8.3.1, >= 8.3.2, >= 8.4.0, >= 8.4.1, >= 8.4.2, >= 8.5.0, >= 8.5.1, >= 8.0.0 < 8.3.3, >= 8.4.0 < 8.4.3. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Check all affected Confluence instances for evidence of compromise per vendor instructions and report any positive findings to CISA.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.