DockerApplication
CVE-2017-14992
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 · uneditedLack of content verification in Docker-CE (Also known as Moby) versions 1.12.6-0, 1.10.3, 17.03.0, 17.03.1, 17.03.2, 17.06.0, 17.06.1, 17.06.2, 17.09.0, and earlier allows a remote attacker to cause a Denial of Service via a crafted image layer payload, aka gzip bombing.
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 · moderate confidenceDocker-CE fails to validate the decompression ratio of image layer payloads, allowing a remote attacker to embed a gzip bomb (highly compressed data that expands to huge size when decompressed) in a malicious image layer. When Docker processes this layer, it attempts to decompress the entire payload into memory or disk, causing resource exhaustion and denial of service.
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
<= 1.10.3= 1.12.6-0= 17.03.0= 17.03.1= 17.03.2= 17.06.0= 17.06.1= 17.06.2= 17.09.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Docker versionRun `docker --version` or `dockerd --version` to get the exact Docker version stringAffected if The version matches one of the affected versions: <= 1.10.3, 1.12.6-0, 17.03.0, 17.03.1, 17.03.2, 17.06.0, 17.06.1, 17.06.2, or 17.09.0
-
Confirm Docker daemon is in useCheck that the Docker daemon (dockerd) is running with `ps aux | grep dockerd` or `systemctl status docker`Affected if Docker daemon is running and the version is in the affected list above
-
Identify if image pulls are allowedReview Docker configuration for allowed pull sources: check /etc/docker/daemon.json for registry settings, or inspect access controls on private registriesAffected if The daemon can pull or load images from untrusted sources and the version is affected
-
Check for layer decompression behaviorAttempt to pull a known test image and monitor memory/disk usage during layer extraction with `docker pull` and system monitoring toolsAffected if Docker decompresses layers without ratio validation, causing excessive resource consumption
You are affected if running a Docker version in the affected list (1.10.3 and below, 1.12.6-0, or 17.03.0-17.09.0) and pulling untrusted image layers that could contain gzip bombs.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Docker-CE to a version beyond 17.09.0 that implements content verification and size limits for image layer decompression, or implement layer size validation at the registry/pull pipeline level before Docker processes the image.
Fix this in Docker
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-14992 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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