CVE-2019-3397
No exploitation reported by the sources we read.
- Published2019-06-03
- Fixed in6.1.2 · 6.0.3 · 5.16.3 · 5.15.3 · 5.14.4 · 5.13.6
- WeaknessCWE-22
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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 before 5.14.4 (fixed version for 5.14.x), from 5.15.0 before 5.15.3 (fixed version for 5.15.x), from 5.16.0 before 5.16.3 (fixed version for 5.16.x), from 6.0.0 before 6.0.3 (fixed version for 6.0.x), and from 6.1.0 before 6.1.2 (the fixed version for 6.1.x) allow remote attackers who have admin permissions to achieve remote code execution on a Bitbucket server instance via path traversal through the Data Center migration tool.
Timeline
dates in UTC- 2019-06-0314:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-3397?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-3397?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.1 | ≥ 6.1.0, < 6.1.2 | 6.1.2 | NVD |
| 6.0 | ≥ 6.0.0, < 6.0.3 | 6.0.3 | NVD |
| 5.16 | ≥ 5.16.0, < 5.16.3 | 5.16.3 | NVD |
| 5.15 | ≥ 5.15.0, < 5.15.3 | 5.15.3 | NVD |
| 5.14 | ≥ 5.14.0, < 5.14.4 | 5.14.4 | NVD |
| 5.13 | ≥ 5.13.0, < 5.13.6 | 5.13.6 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Atlassian bitbucket to 6.1.2 · 6.0.3 · 5.16.3 · 5.15.3 · 5.14.4 · 5.13.6
Advisories and patches
- jira.atlassian.comMitigation · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.09.1read 2026-10-23
- NVDCVSS 2.09read 2026-10-23
- NVDweakness (CWE)CWE-22read 2026-10-23
- FIRST EPSSEPSS score4.4 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- Published
- 2019-06-03
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-3397?
Is CVE-2019-3397 actively exploited?
What is the CVSS score for CVE-2019-3397?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.