dbcve.org
DockerApplication

CVE-2014-3499

HIGH · 7.2 CVSS v2.0 Published 2014-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

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.0.0 creates its management socket with world-readable and world-writable (likely 0777) permissions, allowing any local user on the system to access the Docker daemon's management interface and potentially execute commands with elevated privileges.

MitigationUpgrade Docker to a version where socket permissions are restricted (1.0.1+) or manually set restrictive permissions on the Docker socket (e.g., chmod 660 or 600).

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.0.0
FedoraOperating system
Affected:= 19= 20

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

AV:L/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 Docker version
    Run `docker --version` or inspect the docker package version on the system
    Affected if Docker version is exactly 1.0.0 (the only affected version per vendor records)
  2. Locate Docker socket file
    Check for the presence of /var/run/docker.sock or the socket path used by the Docker daemon on the system
    Affected if The Docker management socket exists at /var/run/docker.sock (or equivalent path)
  3. Verify socket file permissions
    Run `ls -la /var/run/docker.sock` or use `stat /var/run/docker.sock` to examine the file mode bits
    Affected if The socket permissions are 0777 (world-readable and world-writable) or otherwise allow any local user read/write access
  4. Confirm unrestricted access
    Use `getfacl /var/run/docker.sock` or manually verify that the socket lacks restrictive ACLs or ownership restrictions
    Affected if No Access Control List (ACL) or ownership restrictions prevent any local user from accessing the Docker daemon interface

A system is affected if Docker 1.0.0 is installed and the Docker socket file grants world-readable/world-writable permissions, allowing any local user to potentially interact with the Docker daemon.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Docker to a version where socket permissions are restricted (1.0.1+) or manually set restrictive permissions on the Docker socket (e.g., chmod 660 or 600).

Fix this in Docker Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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