dbcve.org
DockerApplication

CVE-2014-9357

HIGH · 10.0 CVSS v2.0 Published 2014-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build in a Dockerfile in an LZMA (.xz) archive, related to the chroot for archive extraction.

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

Docker 1.3.2 contains a vulnerability in its archive extraction mechanism where specially crafted LZMA-compressed (.xz) archives containing malicious Dockerfiles or images can lead to arbitrary code execution with root privileges due to improper chroot handling during extraction.

MitigationUpgrade Docker to a version beyond 1.3.2 (the vulnerability was patched in subsequent releases); avoid pulling or building images from untrusted sources until the upgrade is complete.

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.3.2

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Check installed Docker version
    Run 'docker --version' or 'docker version' to retrieve the installed Docker version number
    Affected if The version displayed is exactly 1.3.2
  2. Verify Docker daemon is operational
    Run 'docker info' to confirm the Docker daemon is running and accessible
    Affected if Docker daemon responds successfully, meaning the vulnerable extraction code is active
  3. Confirm the specific vulnerable release
    Compare your exact Docker version to the affected range: Docker 1.3.2 (only this specific version is affected)
    Affected if Your installed version is exactly 1.3.2, not a newer patched release

You are affected if your Docker installation is version 1.3.2 exactly; later versions (1.3.3 and beyond) contain the patch for this vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Docker to a version beyond 1.3.2 (the vulnerability was patched in subsequent releases); avoid pulling or building images from untrusted sources until the upgrade is complete.

Recommended fix High confidence

Docker 1.3.3 or later

  1. Check current Docker version to confirm it's 1.3.2: docker --version
  2. Stop any running Docker containers: docker stop $(docker ps -aq)
  3. Upgrade Docker to version 1.3.3 or later using your system's package manager (e.g., apt-get, yum, or the appropriate installation method for your OS)
  4. Verify the upgrade was successful: docker --version
  5. Restart the Docker service: sudo service docker restart (or systemctl restart docker)
  6. Verify Docker is functioning normally: docker run hello-world

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9357 — 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-2014-9357 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