dbcve.org
DockerApplication

CVE-2020-14300

HIGH · 8.8 CVSS v3.1 Published 2020-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Red Hat's docker-1.13.1-108.git4ef4b30.el7 package for RHEL 7 included a version of runc that was missing the fix for CVE-2016-9962, a security regression from a previously fixed state (RHSA-2017:0116). This could allow a containerized process to escape and execute arbitrary code on the container host or compromise other containers on the same host.

MitigationUpdate to a later Docker version or roll back to the earlier fixed version (before docker-1.13.1-108.git4ef4b30.el7) since only this single specific version is affected.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DockerApplication
Affected:= 1.13.1
Enterprise Linux ServerOperating system
Affected:= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the operating system is RHEL 7
    Run 'cat /etc/redhat-release' or 'hostnamectl' to confirm the OS version is Red Hat Enterprise Linux Server 7.x
    Affected if The OS is not RHEL 7.x, then this specific vulnerability does not apply
  2. Check if Docker package is installed
    Run 'rpm -qa | grep docker' or 'rpm -q docker' to list installed docker packages
    Affected if Docker is not installed at all, the vulnerability does not apply
  3. Identify the exact Docker package version
    Run 'rpm -q --queryformat "%{VERSION}-%{RELEASE}" docker' or check the full package name with 'rpm -qa | grep -i docker' to get the exact version-release string (e.g., docker-1.13.1-108.git4ef4b30.el7)
    Affected if The installed version is docker-1.13.1-108.git4ef4b30.el7 exactly - this is the only version confirmed affected
  4. Confirm Docker daemon is running
    Run 'systemctl status docker' or 'docker version' to verify the Docker daemon is active and containers can be spawned
    Affected if Docker daemon is not running, the container escape cannot be exploited though the vulnerable binary is still present
  5. Check the runc version if accessible
    Run 'runc --version' if runc is installed separately, though in this specific package docker-1.13.1-108.git4ef4b30.el7 the runc binary is bundled and the version may not be directly queryable
    Affected if Unable to determine runc version indicates it is the bundled version from the affected docker package

You are affected only if you are running RHEL 7 with the exact package version docker-1.13.1-108.git4ef4b30.el7 installed and the Docker daemon is operational.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a later Docker version or roll back to the earlier fixed version (before docker-1.13.1-108.git4ef4b30.el7) since only this single specific version is affected.

Fix this in Docker Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14300 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data