CVE-2019-15012· NVD / CVE Program· CNA atlassian

Bitbucket Server and Bitbucket Data Center from version 4.13.

Noroxi assessment

Priority: Monitor (action score 35/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.5% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Bitbucket Server and Bitbucket Data Center from version 4.13. before 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, from version 6.9.0 before 6.9.1 had a Remote Code Execution vulnerability via the edit-file request. A remote attacker with write permission on a repository can write to any arbitrary file to the victims Bitbucket Server or Bitbucket Data Center instance using the edit-file endpoint, if the user has Bitbucket Server or Bitbucket Data Center running, and has the permission to write the file at that destination. In some cases, this can result in execution of arbitrary code by the victims Bitbucket Server or Bitbucket Data Center instance.

HighCVSS 8.8 · v3.1—No exploit No fix recorded

Published: Jan 15, 2020
Updated: Jun 16, 2026
EPSS: 1.5% · 75th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
atlassian	bitbucket	cpe:2.3:a:atlassian:bitbucket

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

atlassian bitbucket4.13.0 and later · before 5.6.11
atlassian bitbucket6.0.0 and later · before 6.0.11
atlassian bitbucket6.1.0 and later · before 6.1.9
atlassian bitbucket6.2.0 and later · before 6.2.7
atlassian bitbucket6.3.0 and later · before 6.3.6
atlassian bitbucket6.4.0 and later · before 6.4.4
atlassian bitbucket6.5.0 and later · before 6.5.3
atlassian bitbucket6.6.0 and later · before 6.6.3
atlassian bitbucket6.7.0 and later · before 6.7.3
atlassian bitbucket6.8.0 and later · before 6.8.2
atlassian bitbucket6.9.0 and later · before 6.9.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.

Atlassian Bitbucket Data Center
- 4.13 and later · before unspecifiedaffected
- unspecified and later · before 5.16.11affected
- 6.0 and later · before unspecifiedaffected
- unspecified and later · before 6.0.11affected
- 6.1.0 and later · before unspecifiedaffected
- unspecified and later · before 6.1.9affected
- 6.2.0 and later · before unspecifiedaffected
- unspecified and later · before 6.2.7affected
- 6.3.0 and later · before unspecifiedaffected
- unspecified and later · before 6.3.6affected
Atlassian Bitbucket Server
- 4.13 and later · before unspecifiedaffected
- unspecified and later · before 5.16.11affected
- 6.0 and later · before unspecifiedaffected
- unspecified and later · before 6.0.11affected
- 6.1.0 and later · before unspecifiedaffected
- unspecified and later · before 6.1.9affected
- 6.2.0 and later · before unspecifiedaffected
- unspecified and later · before 6.2.7affected
- 6.3.0 and later · before unspecifiedaffected
- unspecified and later · before 6.3.6affected

Same product

atlassian: all records

Other highest-scoring records for the same primary product.

CVE-2022-36804Multiple API endpoints in Atlassian Bitbucket Server and Data Center 7.0.0 before version 7.6.17, from version 7.7.0 before version 7.17.10,KEV
95Now
CVE-2022-43781There is a command injection vulnerability using environment variables in Bitbucket Server and Data Center.
68This week
CVE-2019-15000The 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 (
41Plan

Published before and after this one in the same product

← EarlierCVE-2019-3397Jun 3, 2019 · 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 be
37Monitor
← EarlierCVE-2019-15010Jan 15, 2020 · 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, fr
36Monitor
Later →CVE-2019-20097Jan 15, 2020 · Bitbucket Server and Bitbucket Data Center versions starting from 1.0.0 before 5.16.11, from version 6.0.0 before 6.0.11, from version 6.1.0
36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

AtlassianBugcrowd · paid · up to $12,000

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

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

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Abuse Elevation Control MechanismT1548

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

jira.atlassian.com/browse/BSERV-12100

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records