dbcve.org
DockerApplication

CVE-2014-9358

MEDIUM · 6.4 CVSS v2.0 Published 2014-12-16
Fix available
A fix is available. Upgrade to after 1.3.2 or later.
See remediation →
73/100
Remediation priority · Elevated
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 before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2) "registry communications."

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 before 1.3.3 fails to properly validate image IDs during image loading operations and registry communications, allowing attackers to inject malicious paths via crafted images and perform path traversal attacks or spoof legitimate repositories.

MitigationUpgrade Docker to version 1.3.3 or later which implements proper image ID validation; if immediate upgrade is infeasible, restrict docker load operations and registry communications to only trusted and verified image sources.

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
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/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 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 Docker client and daemon version numbers
    Affected if Version is 1.3.2 or earlier (the client version alone is sufficient as both client and daemon <=1.3.2 are affected)
  2. Verify docker daemon network exposure
    Check if the Docker daemon is listening on a network interface by reviewing dockerd startup arguments, systemd service files, or running 'ss -tlnp | grep docker' or 'netstat -tlnp | grep docker' to inspect listening ports
    Affected if Docker daemon is bound to 0.0.0.0 or an IP accessible from untrusted networks, enabling remote attackers to interact with the daemon
  3. Identify image source configuration
    Examine /etc/docker/daemon.json or docker daemon startup flags for registry configuration. Review any configured insecure registries using 'docker info'
    Affected if Insecure registries are configured or no registry authentication/verification is enforced

You are affected if your Docker version is 1.3.2 or earlier AND the daemon can load images from untrusted sources or is network-accessible to untrusted parties.

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
Upgrade available Upgrade to a release after 1.3.2
Interim mitigation

Upgrade Docker to version 1.3.3 or later which implements proper image ID validation; if immediate upgrade is infeasible, restrict docker load operations and registry communications to only trusted and verified image sources.

Fix this in Docker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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