dbcve.org
DockerApplication

CVE-2014-5282

HIGH · 8.1 CVSS v3.0 Published 2018-02-06
Fix available
A fix is available. Upgrade to 1.3 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 does not properly validate image IDs, which allows remote attackers to redirect to another image through the loading of untrusted images via 'docker load'.

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 version 1.3 lacks proper validation of image IDs during the 'docker load' operation. When loading untrusted images, an attacker could potentially redirect the system to load a different image than intended by manipulating or spoofing image IDs, leading to execution of unauthorized or malicious images.

MitigationUpgrade Docker to version 1.3 or later, which contains proper image ID validation. Avoid loading images from untrusted sources and implement image verification procedures before loading any container images.

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

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Docker daemon version
    Run 'docker version' or 'docker --version' to identify the installed Docker version
    Affected if The Docker version is earlier than 1.3 (e.g., 1.2, 1.2.x, 1.1, etc.)
  2. Verify docker load command availability
    Run 'docker load --help' to confirm the docker load functionality exists in the environment
    Affected if The docker load command is available and the Docker version is below 1.3
  3. Review image loading sources
    Inspect any scripts, CI/CD pipelines, or documentation that reference 'docker load' operations to identify if images from external or untrusted sources are being loaded
    Affected if The docker load operation is used to import images from sources that are not cryptographically verified or are considered untrusted

If Docker version is below 1.3 and the docker load feature is used to import container images, the environment is vulnerable to image ID manipulation and potential execution of unauthorized images.

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 1.3 or later
Fixed in 1.3
Interim mitigation

Upgrade Docker to version 1.3 or later, which contains proper image ID validation. Avoid loading images from untrusted sources and implement image verification procedures before loading any container images.

Fix this in Docker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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