# CVE-2020-14300: Privilege escalation in Docker

> A regression in Red Hat Docker packages reintroduced a container escape vulnerability, allowing attackers to execute arbitrary code on the host.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-26mh-fmrh-48w9

## What is CVE-2020-14300?

CVE-2020-14300 is a high-severity vulnerability in Redhat Enterprise Linux Server, published on 13 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The docker packages version docker-1.13.1-108.git4ef4b30.el7 as released for Red Hat Enterprise Linux 7 Extras via RHBA-2020:0053 (https://access.redhat.com/errata/RHBA-2020:0053) included an incorrect version of runc that was missing multiple bug and security fixes. One of the fixes regressed in that update was the fix for CVE-2016-9962, that was previously corrected in the docker packages in Red Hat Enterprise Linux 7 Extras via RHSA-2017:0116 (https://access.redhat.com/errata/RHSA-2017:0116). The CVE-2020-14300 was assigned to this security regression and it is specific to the docker packages produced by Red Hat. The original issue - CVE-2016-9962 - could possibly allow a process inside container to compromise a process entering container namespace and execute arbitrary code outside of the container. This could lead to compromise of the container host or other containers running on the same container host. This issue only affects a single version of Docker, 1.13.1-108.git4ef4b30, shipped in Red Hat Enterprise Linux 7. Both earlier and later versions are not affected.

Weakness: CWE-273 (Improper Check for Dropped Privileges)

## Which versions are affected by CVE-2020-14300?

It affects 2 products.


Products: Docker Docker, Redhat Enterprise Linux Server.

## How do I fix CVE-2020-14300?

Upgrade to a fixed version.

## Is CVE-2020-14300 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux Server

- [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-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)
- [CVE-2019-13139](https://insights.sbomify.com/CVE-2019-13139/): Command injection in n/a (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14300 and fix it if it is affected.

What it is: CVE-2020-14300 is a high-severity vulnerability in Redhat Enterprise Linux Server, published on 13 Jul 2020. 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-2020-14300 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux Server. 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-2020-14300/ (Markdown: https://insights.sbomify.com/CVE-2020-14300/index.md)
```

## Sources

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

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