dbcve.org
BitbucketApplication · Atlassian

CVE-2019-15000

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-19
Fix available
A fix is available. Upgrade to 5.16.10 / 6.0.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
The commit diff rest endpoint in Bitbucket Server and Data Center before 5.16.10 (the fixed version for 5.16.x ), from 6.0.0 before 6.0.10 (the fixed version for 6.0.x), from 6.1.0 before 6.1.8 (the fixed version for 6.1.x), from 6.2.0 before 6.2.6 (the fixed version for 6.2.x), from 6.3.0 before 6.3.5 (the fixed version for 6.3.x), from 6.4.0 before 6.4.3 (the fixed version for 6.4.x), and from 6.5.0 before 6.5.2 (the fixed version for 6.5.x) allows remote attackers who have permission to access a repository, if public access is enabled for a project or repository then attackers are able to exploit this issue anonymously, to read the contents of arbitrary files on the system and execute commands via injecting additional arguments into git commands.

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-78

User input reaches a shell or system command without being fully separated from the command itself, so an attacker can append their own instructions. Because these run with the application's privileges, it often means full control of the host. The lasting fix is to avoid the shell entirely — call APIs directly and pass arguments as data, never as concatenated strings.

General guidance for the os command injection 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
BitbucketApplication
Affected:>= 5.16.0, < 5.16.10>= 6.0.0, < 6.0.10>= 6.1.0, < 6.1.8>= 6.2.0, < 6.2.6>= 6.3.0, < 6.3.5>= 6.4.0, < 6.4.3>= 6.5.0, < 6.5.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.1/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 5.16.10 / 6.0.10 / 6.1.8 or later
Fixed in 5.16.106.0.106.1.8
Recommended fix High confidence

Upgrade to 5.16.10, 6.0.10, 6.1.8, or 6.2.6 (or later) depending on your current major version branch

  1. 1. Identify the currently installed Bitbucket Server or Data Center version by checking the administration console or using the /rest/api/1.0/application-properties endpoint
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release: if 5.16.x, upgrade to 5.16.10; if 6.0.x, upgrade to 6.0.10; if 6.1.x, upgrade to 6.1.8; if 6.2.x, upgrade to 6.2.6
  3. 3. Review Bitbucket upgrade documentation for your specific version migration path
  4. 4. Perform a full backup of the Bitbucket home directory and database before upgrading
  5. 5. Download the appropriate Bitbucket Server or Data Center installation artifact from the official Atlassian download center
  6. 6. Follow Atlassian's standard upgrade procedure for your installation type (Server or Data Center)
  7. 7. After upgrade, verify the version number matches the expected fixed release
  8. 8. If public repository access was enabled, review and restrict it if not strictly necessary after patching
Caveat Standard Bitbucket minor version upgrades typically have low risk, but review Atlassian's upgrade notes for any behavior changes between your current and target version

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-15000 — 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-15000 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