DockerApplication
CVE-2014-0047
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.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage.
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 before version 1.5 contains unsafe /tmp usage that allows local users to exploit temporary file handling for unspecified impact. The vulnerability stems from improper handling of temporary files in the /tmp directory, which local attackers can potentially manipulate for privilege escalation or other local privilege escalation attacks.
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.4.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Docker versionRun 'docker --version' or 'docker version' to determine the Docker version numberAffected if Version is 1.4.1 or earlier (any version <= 1.4.1)
-
Verify Docker daemon accessibilityCheck if local unprivileged users can interact with the Docker daemon (check docker group membership or socket permissions with 'ls -la /var/run/docker.sock')Affected if Local users have access to the Docker daemon without elevated privileges
-
Inspect /tmp directory permissionsRun 'ls -ld /tmp' to verify the sticky bit is set (should show 'drwxrwxrwt' or similar with the 't' flag)Affected if The sticky bit (1777) is not properly set on /tmp, or /tmp has weak permissions allowing user-specific temp file manipulation
-
Check for exploitable temp file patternsReview Docker's temporary file creation behavior - examine /tmp for any docker-related temporary files that may be world-writable or guessableAffected if Docker creates temporary files in /tmp with predictable names or insecure permissions that local users can manipulate
A system is affected if Docker version 1.4.1 or earlier is installed AND local users have access to the Docker daemon AND /tmp has weak permissions, allowing potential temp file manipulation for privilege escalation.
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.5 or later. If immediate upgrading is not feasible, restrict local user access to Docker daemons and ensure /tmp directories have appropriate sticky-bit permissions (1777) to prevent user-specific temporary file manipulation.
Fix this in Docker
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0047 — 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-0047 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