LiveActive security incident?Get immediate response
CVE Record

CVE-2014-5278: A vulnerability exists in Docker before 1.2 via container names, which may collide with and override contai...

A vulnerability exists in Docker before 1.2 via container names, which may collide with and override container IDs.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns very old Docker versions before 1.2. A container name could collide with a container ID and override it, creating ambiguity in container management. Business urgency depends on whether any legacy Docker hosts still exist; modern supported Docker deployments are unlikely to be affected based on the supplied description.

Executive priority

Prioritize as a legacy exposure discovery task. It is not enough evidence for emergency response, but any production host running Docker before 1.2 should be treated as unsupported and remediated promptly.

Technical view

The CVE description identifies a Docker pre-1.2 flaw where container names may collide with and override container IDs. The bundle provides no CVSS, CWE, affected CPEs, patch details, or verified exploit status. Treat this as a legacy container-management integrity issue until vendor guidance confirms exact impact and remediation.

Likely exposure

Exposure is most likely limited to environments still running Docker before 1.2 or retaining legacy container hosts. The supplied affected-product metadata is incomplete, so asset inventory is required before assigning business impact.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. A public GitHub reference exists, but the bundle does not provide enough content to characterize exploit maturity or real-world use.

Researcher notes

The public CVE record is sparse: no CVSS, CWE, CPE, or detailed root-cause data is supplied. Analysis should avoid assuming broader Docker versions, active exploitation, or specific exploit mechanics beyond the stated name and ID collision behavior.

Mitigation direction

  • Identify any Docker installations older than version 1.2.
  • Check Docker vendor announcement and guidance for the fixed release.
  • Upgrade legacy Docker hosts to a supported release path.
  • Restrict Docker daemon and administrative access during assessment.
  • Retire unsupported legacy container hosts where upgrade is impractical.

Validation and detection

  • Inventory container hosts and record Docker engine versions.
  • Flag any Docker version reported as older than 1.2.
  • Review whether legacy systems rely on container names for administrative actions.
  • Confirm remediation against the Docker announcement or vendor advisory.
  • Document compensating controls for any host that cannot be upgraded.
Prepared
Confidence
medium
Sources
5

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