LiveActive security incident?Get immediate response
CVE Record

CVE-2014-8178: Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 do not use a globally unique identifier to...

Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 do not use a globally unique identifier to store image layers, which makes it easier for attackers to poison the image cache via a crafted image in pull or push commands.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects very old Docker Engine releases that could store image layers without a globally unique identifier. A crafted image used during pull or push operations could make cache poisoning easier, potentially causing systems to reuse the wrong image data.

Executive priority

Treat this as a legacy-container hygiene issue. It is not supported by active-exploitation evidence here, but affected hosts are far past normal support expectations and should be upgraded or retired.

Technical view

Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 used non-globally-unique identifiers for image layer storage. The CVE describes a crafted image cache-poisoning condition reachable through image pull or push workflows. The bundle does not provide CVSS, CWE, exploit maturity, or detailed remediation notes beyond fixed version boundaries.

Likely exposure

Exposure is mainly legacy Docker Engine before 1.8.3 or CS Docker Engine before 1.6.2-CS7. Highest concern is old CI, build, registry, or deployment hosts that pull or push images from untrusted or shared sources.

Exploitation context

The provided sources do not indicate known active exploitation, and the CVE is not marked in KEV. The described attack depends on crafted image interaction through pull or push commands, but the bundle does not provide exploit details or observed campaigns.

Researcher notes

The source bundle is sparse: no CVSS, CWE, proof-of-concept, or detailed root-cause advisory text is included. Analysis should stay anchored to the CVE description and fixed-version boundaries unless vendor advisories add detail.

Mitigation direction

  • Upgrade Docker Engine to 1.8.3 or later where applicable.
  • Upgrade CS Docker Engine to 1.6.2-CS7 or later where applicable.
  • Check Docker vendor guidance for supported upgrade paths and advisories.
  • Retire or isolate legacy Docker hosts that cannot be upgraded.
  • Restrict image sources to trusted registries for remaining legacy systems.

Validation and detection

  • Inventory Docker Engine versions across hosts, CI runners, and build infrastructure.
  • Identify any CS Docker Engine deployments and compare against 1.6.2-CS7.
  • Review systems that pull or push images from shared or untrusted registries.
  • Confirm package or platform records show the fixed version or later.
  • Document any unsupported legacy hosts as accepted or remediated risk.
Prepared
Confidence
medium
Sources
4

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-8178 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
4Source links

CVSS and timeline data

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DockerDocker Enginebefore 1.8.3Listed
DockerCS Docker Enginebefore 1.6.2-CS7Listed
Weakness

CWE details

No CWE listed

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