dbcve.org
ConfluenceApplication · Atlassian

CVE-2019-3395

CRITICAL · 9.8 CVSS v3.0 Published 2019-03-25
Fix available
A fix is available. Upgrade to 6.6.12 / 6.12.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
The WebDAV endpoint in Atlassian Confluence Server and Data Center before version 6.6.7 (the fixed version for 6.6.x), from version 6.7.0 before 6.8.5 (the fixed version for 6.8.x), and from version 6.9.0 before 6.9.3 (the fixed version for 6.9.x) allows remote attackers to send arbitrary HTTP and WebDAV requests from a Confluence Server or Data Center instance via Server-Side Request Forgery.

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
How this class of weakness works · CWE-918

The server can be induced to make requests to a URL an attacker controls, turning it into a proxy into internal networks and cloud metadata services. It's especially dangerous behind a trusted network boundary. The fix is strict allow-listing of destinations and blocking access to internal address ranges.

General guidance for the server-side request forgery (ssrf) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
ConfluenceApplication
Affected:< 6.6.12>= 6.7.0, < 6.12.3
Confluence ServerApplication
Affected:>= 6.13.0, < 6.13.3>= 6.14.0, < 6.14.2

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 · scoped
Upgrade available Upgrade to 6.6.12 / 6.12.3 / 6.13.3 or later
Fixed in 6.6.126.12.36.13.3
Vendor patch jira.atlassian.com →
Recommended fix High confidence

6.6.12, 6.8.5, 6.12.3, 6.13.3, or 6.14.2 depending on current version branch

  1. 1. Identify the currently installed Confluence version by checking the Confluence administration console or running 'confluence --version' from the Confluence home directory
  2. 2. Determine which upgrade path applies based on your current version: if < 6.6.x, upgrade to 6.6.12; if >= 6.7.0 and < 6.8.x, upgrade to 6.8.5; if >= 6.9.0 and < 6.12.x, upgrade to 6.12.3; if >= 6.13.0 and < 6.13.3, upgrade to 6.13.3; if >= 6.14.0 and < 6.14.2, upgrade to 6.14.2
  3. 3. Review Atlassian's upgrade documentation and release notes for your target version at https://confluence.atlassian.com/doc/upgrading-confluence-207896198.html
  4. 4. Perform a full backup of your Confluence database and home directory before upgrading
  5. 5. Download the target Confluence version from https://www.atlassian.com/software/confluence/download-archives
  6. 6. Stop the Confluence service
  7. 7. Follow the standard Confluence upgrade procedure: run the installer or extract the new files, then start Confluence
  8. 8. Verify the upgrade was successful by logging into the administration console and checking the version number
Caveat Standard Confluence minor version upgrades typically have minimal breaking changes, but review release notes for any feature deprecations or configuration changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-3395 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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