# CVE-2019-13139: Command injection in n/a

> Attackers can execute arbitrary commands by manipulating build paths in Docker, leading to code execution on the host system.

- **Severity:** High 8.4 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-13139, GHSA-33j8-c2xf-8225, RHBA-2019:3092

## What is CVE-2019-13139?

CVE-2019-13139 is a high-severity command injection vulnerability in n/a, published on 22 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docker` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |
| `docker-client` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |
| `docker-common` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |
| `docker-debuginfo` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |
| `docker-logrotate` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |
| `docker-lvm-plugin` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |
| `docker-novolume-plugin` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |
| `docker-rhel-push-plugin` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |
| `docker-v1.10-migrator` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-104.git4ef4b30.el7 |

Products: Docker Docker.

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

Upgrade to a fixed version.

## Is CVE-2019-13139 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-9357](https://insights.sbomify.com/CVE-2014-9357/): Arbitrary Code Execution (critical 10.0)
- [CVE-2020-14298](https://insights.sbomify.com/CVE-2020-14298/): Privilege escalation in Docker (high 8.8)
- [CVE-2020-14300](https://insights.sbomify.com/CVE-2020-14300/): Privilege escalation in Docker (high 8.8)
- [CVE-2018-15514](https://insights.sbomify.com/CVE-2018-15514/): Deserialization in n/a (high 8.8)
- [CVE-2014-9356](https://insights.sbomify.com/CVE-2014-9356/): Path Traversal in Docker (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13139 is a high-severity command injection vulnerability in n/a, published on 22 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13139 in the wild and no public exploit code.

Affected product: n/a. 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-13139/ (Markdown: https://insights.sbomify.com/CVE-2019-13139/index.md)
```

## Sources

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

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