CVE-2020-14300

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
30.3%
KEV
Not listed

Published

July 13, 2020

Last Modified

November 21, 2024

References (8)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-08 15:11 UTCEPSS rescore
  4. 2026-07-07 13:43 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-06 02:20 UTCEPSS rescore
  8. 2026-07-04 06:28 UTCEPSS rescore
  9. 2026-07-01 15:03 UTCOSV refresh
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-29 14:04 UTCEPSS rescore
  15. 2026-06-29 14:04 UTCEPSS rescore
  16. 2026-06-28 14:05 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-27 03:06 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-24 14:03 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 56 more
  1. 2026-06-22 14:23 UTCEPSS rescore
  2. 2026-06-22 14:23 UTCEPSS rescore
  3. 2026-06-21 14:54 UTCEPSS rescore
  4. 2026-06-21 14:54 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-19 19:23 UTCEPSS rescore
  8. 2026-06-19 19:23 UTCEPSS rescore
  9. 2026-06-18 17:50 UTCEPSS rescore
  10. 2026-06-18 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-17 17:50 UTCEPSS rescore
  13. 2026-06-16 17:50 UTCEPSS rescore
  14. 2026-06-16 17:50 UTCEPSS rescore
  15. 2026-06-15 17:46 UTCEPSS rescore
  16. 2026-06-14 23:15 UTCEPSS rescore
  17. 2026-06-14 23:15 UTCEPSS rescore
  18. 2026-06-13 23:43 UTCOSV refresh
  19. 2026-06-13 22:58 UTCEPSS rescore
  20. 2026-06-13 22:58 UTCEPSS rescore
  21. 2026-06-12 23:09 UTCEPSS rescore
  22. 2026-06-11 13:58 UTCEPSS rescore
  23. 2026-06-10 22:16 UTCEPSS rescore
  24. 2026-06-10 22:16 UTCEPSS rescore
  25. 2026-06-10 13:20 UTCEPSS rescore
  26. 2026-06-08 14:15 UTCEPSS rescore
  27. 2026-06-08 14:15 UTCEPSS rescore
  28. 2026-06-07 15:23 UTCEPSS rescore
  29. 2026-06-07 15:23 UTCEPSS rescore
  30. 2026-06-06 13:45 UTCEPSS rescore
  31. 2026-06-06 13:45 UTCEPSS rescore
  32. 2026-06-06 13:45 UTCEPSS rescore
  33. 2026-06-05 22:45 UTCEPSS rescore
  34. 2026-06-05 22:45 UTCEPSS rescore
  35. 2026-06-05 06:08 UTCEPSS rescore
  36. 2026-06-04 13:10 UTCEPSS rescore
  37. 2026-06-04 13:10 UTCEPSS rescore
  38. 2026-06-02 20:11 UTCEPSS rescore
  39. 2026-06-02 20:11 UTCEPSS rescore
  40. 2026-06-01 13:50 UTCEPSS rescore
  41. 2026-05-31 22:29 UTCEPSS rescore
  42. 2026-05-31 22:29 UTCEPSS rescore
  43. 2026-05-31 00:15 UTCEPSS rescore
  44. 2026-05-31 00:14 UTCEPSS rescore
  45. 2026-05-29 13:42 UTCEPSS rescore
  46. 2026-05-29 13:42 UTCEPSS rescore
  47. 2026-05-28 13:43 UTCEPSS rescore
  48. 2026-05-28 13:43 UTCEPSS rescore
  49. 2026-05-27 13:39 UTCEPSS rescore
  50. 2026-05-27 01:28 UTCEG score recompute
  51. 2026-05-27 01:28 UTCVendor advisory
  52. 2026-05-27 01:28 UTCGHSA enrichment
  53. 2026-05-26 13:42 UTCEPSS rescore
  54. 2026-05-26 13:42 UTCEPSS rescore
  55. 2026-05-26 07:17 UTCEPSS rescore
  56. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2020-14300?
CVE-2020-14300 is a high vulnerability published on July 13, 2020. 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…
When was CVE-2020-14300 disclosed?
CVE-2020-14300 was first published in the National Vulnerability Database on July 13, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-14300 actively exploited?
CVE-2020-14300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-14300?
CVE-2020-14300 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2020-14300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-14300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-14300

Explore →

Is Your Infrastructure Affected by CVE-2020-14300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs