CVE-2020-14300
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 31% of all known CVEs.
References
Related Vulnerabilities
Other CWE-273 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2011-2921 | Critical | 9.8 | 83% | - | - |
| CVE-2024-38813 | High | 7.5 | 17% | KEV | Fix |
| CVE-2017-6972 | Critical | 9.8 | 15% | - | - |
| CVE-2015-0278 | High | 10.0 | 3.2% | - | Fix |
| CVE-2019-18276 | High | 7.8 | 2.6% | - | Fix |
| CVE-2021-36372 | Critical | 9.8 | 2.4% | - | Fix |
Common questions
How do I fix CVE-2020-14300?
No published fix for CVE-2020-14300 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2020-14300 being actively exploited?
Not that we know of. CVE-2020-14300 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.38% is the estimated probability that it will be exploited in the next 30 days. That is higher than 31% of all scored CVEs.
How severe is CVE-2020-14300?
CVE-2020-14300 has a CVSS v3 base score of 8.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2020-14300
Markdown
[](https://tridentstack.com/cve/CVE-2020-14300)HTML
<a href="https://tridentstack.com/cve/CVE-2020-14300"><img src="https://tridentstack.com/cve/badge/CVE-2020-14300.svg" alt="CVE-2020-14300"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.