Confluence ServerApplication · Atlassian
CVE-2019-3398
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 · uneditedConfluence 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.
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 · high confidencePath traversal vulnerability in Confluence Server and Data Center's downloadallattachments resource allows authenticated attackers with permissions to add attachments, create spaces, or with Admin space permissions to write files to arbitrary locations, leading to remote code execution.
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 ServerApplication
>= 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.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Confluence installation versionLog in as administrator and navigate to > General Configuration > Confluence Admin > Troubleshooting and support tools, or access the /confluence/about/confluence.json endpoint. Alternatively, check the confluence-admin.properties file in the Confluence home directory.Affected if The installed version falls within any of these ranges: >= 2.0 and < 6.6.13, >= 6.7.0 and < 6.12.4, >= 6.13.0 and < 6.13.4, >= 6.14.0 and < 6.14.3, or >= 6.15.0 and < 6.15.2.
-
Confirm Confluence web interface is accessibleAttempt to access the Confluence base URL over HTTP/HTTPS to verify the application is exposed.Affected if The Confluence web interface responds, indicating the application is network-accessible.
-
Verify the downloadallattachments REST endpoint existsSend a GET request to /rest/api/space/{spaceKey}/downloadallattachments (replace {spaceKey} with a valid space key) using an authenticated account with add attachments, create spaces, or space Admin permissions.Affected if The endpoint responds with a valid HTTP response (200 or 403), confirming the vulnerable resource is present.
-
Check for unusual file writes in Confluence home directoryReview file system timestamps and contents in the Confluence attachments directory (typically <confluence-home>/attachments) for any unexpectedly created files outside expected attachment structures.Affected if Files exist in unexpected locations, particularly in the Confluence installation directory or outside the designated attachments folder.
You are affected if your Confluence Server or Data Center version is below the fixed versions (6.6.13, 6.12.4, 6.13.4, 6.14.3, or 6.15.2) AND the web interface is accessible to users with add attachments, create spaces, or space Admin permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.6.136.12.46.13.4
Upgrade Confluence Server/Data Center to version 6.6.13, 6.12.4, 6.13.4, 6.14.3, or 6.15.2 or later. Alternatively, restrict attachment and space creation permissions until patching can be completed.
Upgrade to Confluence Server 6.6.13, 6.12.4, 6.13.4, 6.14.3, or 6.15.2 (depending on your current major version)
- 1. Identify the current Confluence Server version by checking the atlassian-confluence URL or Confluence administration console
- 2. Based on the current version, determine the appropriate target fixed version: for 6.6.x upgrade to 6.6.13, for 6.7.x-6.12.x upgrade to 6.12.4, for 6.13.x upgrade to 6.13.4, for 6.14.x upgrade to 6.14.3, for 6.15.x upgrade to 6.15.2
- 3. Perform a full backup of the Confluence database and home directory before upgrading
- 4. Review the Atlassian Upgrade Guide for pre-upgrade requirements and considerations
- 5. Download the appropriate fixed version from the Atlassian download center
- 6. Stop the Confluence service
- 7. Install the upgrade following Atlassian's standard upgrade procedure
- 8. Start the Confluence service and verify the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Confluence Server
Exploited in the wild — priority engagement
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3398 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3398 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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