CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2019-3398 remediation guide

Atlassian Confluence Server and Data Center

Confluence Server and Data Center had a path traversal vulnerability in the downloadallattachments resource. A remote attacker who has permission to add attachments to pages and / or blogs or to create a new space or a personal space or who has 'Admin' permissions for a space can exploit this path traversal vulnerability to write files to arbitrary locations which can lead to remote code execution on systems that run a vulnerable version of Confluence Server or Data Center. All versions of Confluence Server from 2.0.0 before 6.6.13 (the fixed version for 6.6.x), from 6.7.0 before 6.12.4 (th...

Open CVE record
ProductAtlassian Confluence Server and Data Center
Affected versions2.0.0, unspecified, 6.7.0, 6.13.0, 6.14.0, 6.15.0, >= 2.0 < 6.6.13, >= 6.7.0 < 6.12.4, >= 6.13.0 < 6.13.4, >= 6.14.0 < 6.14.3, >= 6.15.0 < 6.15.2
Fixed versions6.6.13, 6.12.4, 6.13.4, 6.14.3, 6.15.2
Priority basisImmediate · CVSS 8.8 · EPSS 97.2%
01

Identify the affected asset

Confirm whether Atlassian Confluence Server and Data Center 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.
02

Validate the affected-version match

Compare the deployed version with the affected range: 2.0.0, unspecified, 6.7.0, 6.13.0, 6.14.0, 6.15.0, >= 2.0 < 6.6.13, >= 6.7.0 < 6.12.4, >= 6.13.0 < 6.13.4, >= 6.14.0 < 6.14.3, >= 6.15.0 < 6.15.2. Treat incomplete inventory results as unresolved.

03

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.

04

Apply supported remediation

Apply updates per vendor instructions.

05

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.