# CVE-2019-15012: Path traversal in Bitbucket Data Center

> Remote attackers with write permissions can exploit path traversal in the edit-file endpoint to write arbitrary files, potentially leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4hfv-698v-c974

## What is CVE-2019-15012?

CVE-2019-15012 is a high-severity path traversal vulnerability in Atlassian Bitbucket Data Center, published on 15 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2019-15012?

It affects 1 product.


Products: Atlassian Bitbucket.

## How do I fix CVE-2019-15012?

No fix has been published for CVE-2019-15012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-15012 being exploited?

There is no known exploitation of CVE-2019-15012 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Bitbucket Data Center

- [CVE-2022-36804](https://insights.sbomify.com/CVE-2022-36804/): Atlassian Bitbucket Server and Data Center Command Injection (high 8.8, exploited in the wild)
- [CVE-2018-5225](https://insights.sbomify.com/CVE-2018-5225/): Path traversal in Bitbucket Server (critical 9.9)
- [CVE-2022-43781](https://insights.sbomify.com/CVE-2022-43781/): Command injection in Bitbucket Data Center (critical 9.8)
- [CVE-2019-15000](https://insights.sbomify.com/CVE-2019-15000/): Command injection in Bitbucket Data Center (critical 9.8)
- [CVE-2019-3397](https://insights.sbomify.com/CVE-2019-3397/): Path traversal in Bitbucket Data Center (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15012 and fix it if it is affected.

What it is: CVE-2019-15012 is a high-severity path traversal vulnerability in Atlassian Bitbucket Data Center, published on 15 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15012 in the wild and no public exploit code.

Affected product: Atlassian Bitbucket Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-15012/ (Markdown: https://insights.sbomify.com/CVE-2019-15012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-15012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-15012
- OSV: https://osv.dev/vulnerability/CVE-2019-15012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-15012/
Summaries are generated and may contain mistakes; the official description above is the record.