dbcve.org
BitbucketApplication · Atlassian

CVE-2019-3397

CRITICAL · 9.1 CVSS v3.0 Published 2019-06-03
Fix available
A fix is available. Upgrade to 5.13.6 / 5.14.4 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Atlassian Bitbucket Data Center licensed instances starting with version 5.13.0 before 5.13.6 (the fixed version for 5.13.x), from 5.14.0 before 5.14.4 (fixed version for 5.14.x), from 5.15.0 before 5.15.3 (fixed version for 5.15.x), from 5.16.0 before 5.16.3 (fixed version for 5.16.x), from 6.0.0 before 6.0.3 (fixed version for 6.0.x), and from 6.1.0 before 6.1.2 (the fixed version for 6.1.x) allow remote attackers who have admin permissions to achieve remote code execution on a Bitbucket server instance via path traversal through the Data Center migration tool.

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 confidence

Path traversal vulnerability in Atlassian Bitbucket Data Center's Data Center migration tool allows remote authenticated administrators to achieve remote code execution by manipulating file paths during migration operations. The vulnerability affects multiple version branches from 5.13.x through 6.1.x.

MitigationUpgrade Bitbucket Data Center to the fixed versions (5.13.6, 5.14.4, 5.15.3, 5.16.3, 6.0.3, or 6.1.2) or later. Restrict admin access and review migration tool usage until patching is complete.

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
BitbucketApplication
Affected:>= 5.13.0, < 5.13.6>= 5.14.0, < 5.14.4>= 5.15.0, < 5.15.3>= 5.16.0, < 5.16.3>= 6.0.0, < 6.0.3>= 6.1.0, < 6.1.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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Bitbucket version
    Run 'bitbucket-version.sh' or check the Bitbucket admin UI under 'Administration' > 'Server settings' > 'Application version', or query the REST API endpoint /rest/api/1.0/application-properties
    Affected if The installed version falls within any of these ranges: 5.13.0-5.13.5, 5.14.0-5.14.3, 5.15.0-5.15.2, 5.16.0-5.16.2, 6.0.0-6.0.2, or 6.1.0-6.1.1
  2. Determine if Data Center migration tool is in use
    Check if any migration import operations have been performed recently via Bitbucket audit logs, or check if the /migration/* endpoints are accessible on the instance
    Affected if Migration import operations have been executed on the affected version ranges, allowing path traversal during those operations
  3. Verify administrator access controls
    Review the Bitbucket administration console under 'Administration' > 'Users and groups' to list all users with 'System Admin' or 'Admin' global permissions
    Affected if Any external or untrusted users possess administrative privileges and the Bitbucket version is within the affected ranges

The environment is affected if Bitbucket Data Center is running any version from 5.13.0 through 5.13.5, 5.14.0 through 5.14.3, 5.15.0 through 5.15.2, 5.16.0 through 5.16.2, 6.0.0 through 6.0.2, or 6.1.0 through 6.1.1 and the Data Center migration tool feature has been used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 5.13.6 / 5.14.4 / 5.15.3 or later
Fixed in 5.13.65.14.45.15.3
Interim mitigation

Upgrade Bitbucket Data Center to the fixed versions (5.13.6, 5.14.4, 5.15.3, 5.16.3, 6.0.3, or 6.1.2) or later. Restrict admin access and review migration tool usage until patching is complete.

Recommended fix High confidence

5.13.6 (for 5.13.x), 5.14.4 (for 5.14.x), 5.15.3 (for 5.15.x), 5.16.3 (for 5.16.x), 6.0.3 (for 6.0.x), or 6.1.2 (for 6.1.x)

  1. 1. Identify the current Bitbucket version by checking the Bitbucket administration console or running 'bitbucket --version'
  2. 2. Determine which version branch your instance is running on (5.13.x, 5.14.x, 5.15.x, 5.16.x, 6.0.x, or 6.1.x)
  3. 3. For version 5.13.x: upgrade to version 5.13.6 or later
  4. 4. For version 5.14.x: upgrade to version 5.14.4 or later
  5. 5. For version 5.15.x: upgrade to version 5.15.3 or later
  6. 6. For version 5.16.x: upgrade to version 5.16.3 or later
  7. 7. For version 6.0.x: upgrade to version 6.0.3 or later
  8. 8. For version 6.1.x: upgrade to version 6.1.2 or later
Caveat Standard Bitbucket upgrade considerations apply - review the Atlassian upgrade guide for your version range, particularly note any database migration requirements and backup procedures

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

Fix this in Bitbucket Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3397 — 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-3397 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