dbcve.org
BitbucketApplication · Atlassian

CVE-2019-15010

HIGH · 8.8 CVSS v3.1 Published 2020-01-15
Fix available
A fix is available. Upgrade to 5.6.11 / 6.0.11 or later.
See remediation →
94/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
Bitbucket Server and Bitbucket Data Center versions starting from version 3.0.0 before version 5.16.11, from version 6.0.0 before 6.0.11, from version 6.1.0 before 6.1.9, from version 6.2.0 before 6.2.7, from version 6.3.0 before 6.3.6, from version 6.4.0 before 6.4.4, from version 6.5.0 before 6.5.3, from version 6.6.0 before 6.6.3, from version 6.7.0 before 6.7.3, from version 6.8.0 before 6.8.2, and from version 6.9.0 before 6.9.1 had a Remote Code Execution vulnerability via certain user input fields. A remote attacker with user level permissions can exploit this vulnerability to run arbitrary commands on the victim's systems. Using a specially crafted payload as user input, the attacker can execute arbitrary commands on the victim's Bitbucket Server or Bitbucket Data Center instance.

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

Bitbucket Server and Data Center versions 3.0.0 through 6.9.0 contain a Remote Code Execution vulnerability where user input fields accept specially crafted payloads that allow arbitrary command execution on the host system. A remote attacker with basic user-level permissions can exploit this vulnerability.

MitigationUpgrade Bitbucket Server/Data Center to version 5.16.11, 6.0.11, 6.1.9, 6.2.7, 6.3.6, 6.4.4, 6.5.3, 6.6.3, 6.7.3, 6.8.2, or 6.9.1 or later to remediate this vulnerability.

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:>= 3.0.0, < 5.6.11>= 6.0.0, < 6.0.11>= 6.1.0, < 6.1.9>= 6.2.0, < 6.2.7>= 6.3.0, < 6.3.6>= 6.4.0, < 6.4.4>= 6.5.0, < 6.5.3>= 6.6.0, < 6.6.3>= 6.7.0, < 6.7.3>= 6.8.0, < 6.8.2>= 6.9.0, < 6.9.1

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

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

  1. Locate Bitbucket version from web UI
    Log into Bitbucket and scroll to the footer of any page. The version is displayed as 'Bitbucket <version>' (for example, 'Bitbucket 6.9.0').
    Affected if Version displayed matches any of the affected ranges: >=3.0.0 to <5.6.11, >=6.0.0 to <6.0.11, >=6.1.0 to <6.1.9, >=6.2.0 to <6.2.7, >=6.3.0 to <6.3.6, >=6.4.0 to <6.4.4, >=6.5.0 to <6.5.3, >=6.6.0 to <6.6.3, >=6.7.0 to <6.7.3, >=6.8.0 to <6.8.2, or >=6.9.0 to <6.9.1.
  2. Locate Bitbucket version from about page
    Navigate to the About page: /about (for example, https://your-bitbucket-server/about). The version is shown on this page.
    Affected if Version matches any of the affected ranges listed in step 1.
  3. Locate Bitbucket version from command line
    If you have shell access to the Bitbucket server, run: cd <bitbucket-home>/bin and ./bitbucket-version (or check the 'atlassian-bitbucket' script output). Alternatively, check the 'bitbucket.version' property in <bitbucket-home>/app/data/application.properties.
    Affected if Version matches any of the affected ranges listed in step 1.
  4. Check if user access is enabled
    Review Bitbucket user management settings to confirm that user registration or LDAP/SSO integration is active, allowing basic user-level accounts to log in.
    Affected if User access is enabled and the Bitbucket version is within any of the affected ranges listed in step 1.

If the installed Bitbucket version falls within any of the listed affected ranges and user authentication is enabled, the environment is vulnerable to remote code execution via specially crafted user input.

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.

From vendor data
Upgrade available Upgrade to 5.6.11 / 6.0.11 / 6.1.9 or later
Fixed in 5.6.116.0.116.1.9
Interim mitigation

Upgrade Bitbucket Server/Data Center to version 5.16.11, 6.0.11, 6.1.9, 6.2.7, 6.3.6, 6.4.4, 6.5.3, 6.6.3, 6.7.3, 6.8.2, or 6.9.1 or later to remediate this vulnerability.

Fix this in Bitbucket Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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 locally
dbcve dependency scanner

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