CVE-2019-13139: In Docker before 18.09.4, an attacker who is capable of supplying or manipulating the build path for the "docker build" command would be abl
Noroxi assessment
Priority: Monitor (action score 34/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: 2% (FIRST EPSS); higher than 81.2% of all records.
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: docker.io (Debian:10) 18.09.1+dfsg1-7.1+deb10u1; docker.io (Debian:12) 18.09.1+dfsg1-8; docker (Red Hat:rhel_extras_other:7) 2:1.13.1-104.git4ef4b30.el7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to docker.io (Debian:10) 18.09.1+dfsg1-7.1+deb10u1; docker.io (Debian:12) 18.09.1+dfsg1-8; docker (Red Hat:rhel_extras_other:7) 2:1.13.1-104.git4ef4b30.el7 or later.
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
In Docker before 18.09.4, an attacker who is capable of supplying or manipulating the build path for the "docker build" command would be able to gain command execution. An issue exists in the way "docker build" processes remote git URLs, and results in command injection into the underlying "git clone" command, leading to code execution in the context of the user executing the "docker build" command. This occurs because git ref can be misinterpreted as a flag.
- Published
- Aug 22, 2019
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 81th percentile
- CWE
- CWE-78
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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 |
|---|---|---|
| docker | docker | cpe:2.3:a:docker:docker |
Using docker? Add it to your stack and be the first to know about CVEs like this one. (Docker)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- docker dockerbefore 18.09.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | docker.io | before 18.09.1+dfsg1-7.1+deb10u1 | 18.09.1+dfsg1-7.1+deb10u1 |
| Debian:12 | docker.io | before 18.09.1+dfsg1-8 | 18.09.1+dfsg1-8 |
| Red Hat:rhel_extras_other:7 | docker | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
| Red Hat:rhel_extras_other:7 | docker-client | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
| Red Hat:rhel_extras_other:7 | docker-common | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
| Red Hat:rhel_extras_other:7 | docker-debuginfo | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
| Red Hat:rhel_extras_other:7 | docker-logrotate | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
| Red Hat:rhel_extras_other:7 | docker-lvm-plugin | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
| Red Hat:rhel_extras_other:7 | docker-novolume-plugin | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
| Red Hat:rhel_extras_other:7 | docker-rhel-push-plugin | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
| Red Hat:rhel_extras_other:7 | docker-v1.10-migrator | before 2:1.13.1-104.git4ef4b30.el7 | 2:1.13.1-104.git4ef4b30.el7 |
Same product
docker: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15752Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-credential-wincred.exKEV76This week
- CVE-2019-5736runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequen64This week
- CVE-2019-14271In Docker 19.03.x before 19.03.1 linked against the GNU C Library (aka glibc), code injection can occur when the nsswitch facility dynamical45Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-15664May 23, 2019 · In Docker through 18.06.1-ce-rc2, the API endpoints behind the 'docker cp' command are vulnerable to a symlink-exchange attack with Director31Monitor
- ← EarlierCVE-2019-13509Jul 18, 2019 · In Docker CE and EE before 18.09.8 (as well as Docker EE before 17.06.2-ee-23 and 18.x before 18.03.1-ee-10), Docker Engine in debug mode ma31Monitor
- Later →CVE-2019-16884Sep 25, 2019 · runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/roo31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:docker.io | 18.09.1+dfsg1-8 · Debian:12 | Package registry (OSV) |
| red hat:docker | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-client | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-common | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-debuginfo | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-logrotate | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-lvm-plugin | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-novolume-plugin | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-rhel-push-plugin | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-v1.10-migrator | 2:1.13.1-104.git4ef4b30.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, 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
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-19-137 · Sep 9, 2019(Docker Sunucu Güvenlik Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;
exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;
if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
execFile("ping", ["-c", "1", host], onResult);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)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.