CVE-2019-3398: Atlassian Confluence Server and Data Center Path Traversal Vulnerability
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 (the fixed version for 6.12.x), from 6.13.0 before 6.13.4 (the fixed version for 6.13.x), from 6.14.0 before 6.14.3 (the fixed version for 6.14.x), and from 6.15.0 before 6.15.2 are affected by this vulnerability.
CVE-2019-3398 is a path traversal weakness in Atlassian Confluence Server and Data Center. It affects the downloadallattachments resource and can let a privileged remote attacker write files on the system. Successful abuse can lead to remote code execution, so teams running Confluence should treat it as a priority to inventory and remediate.
Public detail is limited to the vendor and CISA descriptions; confirm exact affected builds, fixed releases, and configuration notes directly against the Atlassian advisory before acting.
How it works
This issue is classed as CWE-22 (path traversal). In products that accept path or filename input for file operations, insufficient validation can let an attacker supply sequences that escape the intended directory and reach other locations on the filesystem.
According to the CISA summary, the flaw sits in the downloadallattachments resource. A privileged remote attacker who can reach that functionality may cause the application to write files outside the expected path. Once arbitrary file write is possible, an attacker can often place executable content or alter application components in ways that achieve remote code execution. Exact request shape, prerequisites beyond privilege, and payload details are not provided here; treat any public proof-of-concept material cautiously and validate behavior only in a lab against the vendor’s description.
Am I affected? How to find it in your systems
Confluence Server and Data Center typically run as internal or internet-facing collaboration platforms, often behind reverse proxies or SSO, on Windows or Linux hosts, and sometimes in clustered Data Center layouts. Inventory every instance:
- Query CMDB, software inventory, and container/orchestration registries for Confluence Server or Data Center installations.
- Check application About/System Information pages, installer records, and package versions on each node; compare them to the fixed versions listed in the Atlassian advisory for CVE-2019-3398.
- Note whether the downloadallattachments (or equivalent attachment bulk-download) functionality is reachable by authenticated privileged users, and whether instances are exposed beyond the corporate network.
For exploitation signs, review Confluence and reverse-proxy access logs for unusual authenticated requests to attachment-download endpoints, unexpected file creation or modification under the Confluence home, temp, or web-root directories, and new or altered scripts/binaries coinciding with privileged sessions. Endpoint detection and file-integrity monitoring on Confluence hosts can surface anomalous writes. Confirm log field names and paths against your version’s documentation.
How to remediate
Patch first. Apply the updates Atlassian released for this CVE, following the vendor’s upgrade instructions for Server and Data Center. CISA’s required action is to apply updates per vendor instructions; schedule maintenance windows, back up spaces and the database, and test the upgrade path in a non-production environment if you run a cluster or have heavy customizations.
After patching, harden for this class of weakness:
- Ensure Confluence runs with least privilege (dedicated service account, no unnecessary OS admin rights).
- Restrict filesystem permissions on the Confluence home, attachments, and install directories so the process cannot write outside intended locations.
- Keep attachment and download features limited to users who need them; review privileged group membership.
- Place instances behind authentication gateways and network controls so only trusted networks and identities can reach administrative or bulk-attachment functions.
If you can't patch immediately
Reduce exposure until you can upgrade:
- Segment Confluence hosts so they are not reachable from the open internet; require VPN or zero-trust access for privileged users.
- If a web application firewall or reverse-proxy filter is available, apply virtual patching rules that block path-traversal patterns (directory ascent sequences and unexpected encodings) on attachment-related URLs; tune to avoid breaking legitimate downloads and confirm against vendor guidance.
- Temporarily disable or restrict the affected downloadallattachments functionality if your process and the product allow it without breaking critical workflows.
- Increase monitoring: alert on privileged access to attachment bulk endpoints, anomalous file writes under the Confluence directories, and post-authentication process execution from the Confluence service account.
- Enforce strong authentication (SSO/MFA) for all privileged Confluence accounts to raise the bar for the “privileged remote attacker” prerequisite.
These steps do not replace the patch; they only buy time.
If your data may have been exposed
Actively exploited path-traversal and file-write flaws can lead to full compromise of the application host and subsequent data theft or ransomware staging. Known ransomware use is not documented for this CVE in the supplied facts, but any confirmed exploitation should trigger your incident-response process: isolate the host, preserve logs and disk evidence, rotate credentials accessible from the instance, and assess attached file stores and integrated systems for unauthorized access. As a routine check, you can run a free exposure scan of your email addresses against known breach data to see whether credentials tied to your organization already appear in public dumps.
AICompiled with AI assistance from public sources and published under our editorial standards.
Details
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HReferences
- packetstormsecurity.com/files/152616/Confluence-Server-Data-Center-Path-Traversa
- packetstormsecurity.com/files/155235/Atlassian-Confluence-6.15.1-Directory-Trave
- packetstormsecurity.com/files/155245/Atlassian-Confluence-6.15.1-Directory-Trave
- www.securityfocus.com/bid/108067
- jira.atlassian.com/browse/CONFSERVER-58102
- seclists.org/bugtraq/2019/Apr/33
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-3398