DockerApplication
CVE-2014-9356
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 · uneditedPath traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection mechanism via a full pathname in a symlink in an (1) image or (2) build in a Dockerfile.
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 confidencePath traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass container protection mechanisms via a full pathname in a symlink within Docker images or during Dockerfile builds.
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.3CVSS 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
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.
-
Check installed Docker versionRun 'docker --version' or 'docker version' to display the Docker client and daemon versionsAffected if The Docker version is earlier than 1.3.3 (e.g., 1.3.2, 1.3.1, 1.3.0, or any version below 1.3.3)
-
Identify all Docker images presentRun 'docker images -a' to list all locally stored Docker imagesAffected if Any image was built or imported using a Docker version earlier than 1.3.3, or contains symlinks referencing absolute paths outside the container
-
Examine image contents for symlinksUse 'docker run --rm <image> ls -la <path>' to inspect symlinks within running containers, or use 'docker save <image>' and inspect the tar contents for symlinks in layer filesAffected if Symlinks in images point to absolute paths on the host filesystem (e.g., symlinks created during 'docker build' or 'docker import' that resolve outside the intended container root)
-
Review recent Dockerfile buildsInspect Dockerfile history using 'docker history <image>' and check any Dockerfiles used to build images for ADD or COPY directives that may have pulled in symlink-containing archivesAffected if Images were built from Dockerfiles or archives using Docker versions prior to 1.3.3
If Docker version is 1.3.3 or later, the environment is not affected by this CVE; if Docker version is earlier than 1.3.3, the environment is affected and may contain malicious symlinks from image builds.
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 data1.3.3
Upgrade Docker to version 1.3.3 or later to patch this vulnerability. Review existing images and build processes for any malicious symlinks that may have been introduced.
Fix this in Docker
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9356 — 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-9356 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