LiveActive security incident?Get immediate response
CVE Record

CVE-2014-5282: Docker before 1.3 does not properly validate image IDs, which allows remote attackers to redirect to anothe...

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'.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Older Docker versions before 1.3 could mishandle image identifiers when importing an untrusted image archive. If an organization still loads external or user-supplied Docker images on legacy hosts, an attacker could redirect the load to a different image than intended.

Executive priority

Treat this as a legacy-container hygiene issue unless evidence shows affected Docker versions or untrusted image-loading workflows. Prioritize inventory first, then remove or isolate any remaining exposure.

Technical view

The CVE states Docker before 1.3 did not properly validate image IDs during docker load of untrusted images, allowing remote attackers to redirect to another image. The provided sources do not include CVSS, CWE, detailed package matrices, or proof of active exploitation.

Likely exposure

Exposure is most plausible on legacy systems running Docker before 1.3 that import image archives from untrusted parties or automated pipelines. Modern supported Docker installations are unlikely to match the described version range, but evidence in the bundle is limited.

Exploitation context

The bundle does not show CISA KEV listing or other evidence of active exploitation. The described condition depends on loading untrusted images, so internet exposure alone is not the main indicator; risky image-import workflows matter more.

Researcher notes

Key missing evidence: CVSS score, CWE classification, affected distribution package details, and exploit telemetry. Validation should focus on version confirmation and whether docker load accepts untrusted archives in build or operations paths.

Mitigation direction

  • Inventory hosts and pipelines for Docker versions before 1.3.
  • Move affected Docker installations to a supported vendor-maintained release.
  • Avoid docker load workflows for untrusted or user-supplied image archives.
  • Review Docker and distribution advisories for package-specific guidance.
  • Restrict image imports to trusted, reviewed sources.

Validation and detection

  • Confirm Docker Engine versions on container hosts and build workers.
  • Identify pipelines or services that load external image archives.
  • Verify untrusted image archives are rejected or isolated before import.
  • Check vendor advisory status for any legacy distribution packages.
  • Document whether any affected workflows remain in production.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-5282 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.