DockerApplication
CVE-2014-6407
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 · uneditedDocker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a (1) symlink or (2) hard link attack in an image archive in a (a) pull or (b) load operation.
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 confidenceDocker before 1.3.2 does not properly validate symlinks and hard links within image archives during pull or load operations. Attackers can craft malicious image archives containing symlinks or hard links that point to arbitrary filesystem locations on the host, enabling arbitrary file writes and potentially remote code execution.
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.3.1= 1.0.0= 1.3.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Docker version numberAffected if The version is 1.0.0, 1.3.0, or any version <= 1.3.1 (for example 1.2.0, 1.1.0, etc.)
-
Confirm Docker daemon is runningRun 'docker info' or check if the Docker service/daemon is active using 'systemctl status docker' or equivalentAffected if The daemon is running and responds to client commands, as the vulnerability is triggered during pull or load operations
-
Check for untrusted image sourcesReview Docker configuration and any registry aliases in /etc/docker/daemon.json or similar config files to identify if untrusted or public registries are accessibleAffected if Users can pull or load images from untrusted or public sources, which is the attack vector for this CVE
-
Verify image pull/load capabilityAttempt a test pull from a non-trusted source or inspect existing images using 'docker images' and 'docker history' to see if user has access to image operationsAffected if The Docker client can pull or load images from archives, as this vulnerability is exploited through malicious image archives during these operations
You are affected if Docker version 1.0.0, 1.3.0, or any version through 1.3.1 is installed and the daemon can pull or load images from potentially untrusted sources.
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 to version 1.3.2 or later, which contains proper validation of archive contents to prevent symlink/hardlink attacks. If immediate upgrade is not possible, only pull or load images from trusted sources.
Fix this in Docker
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6407 — 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-2014-6407 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