LiveActive security incident?Get immediate response
CVE Record

CVE-2014-5279: The Docker daemon managed by boot2docker 1.2 and earlier improperly enables unauthenticated TCP connections...

The Docker daemon managed by boot2docker 1.2 and earlier improperly enables unauthenticated TCP connections by default, which makes it easier for remote attackers to gain privileges or execute arbitrary code from children containers.

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

Security readout for executives and security teams

Plain-English summary

CVE-2014-5279 concerns boot2docker 1.2 and earlier starting the Docker daemon with unauthenticated TCP access enabled by default. If that interface is reachable, a remote attacker could potentially control container activity, gain privileges, or execute arbitrary code through child containers. The issue is old, but exposed legacy installations should be treated seriously.

Executive priority

Prioritize if the organization still has legacy boot2docker systems, especially in development, CI, or lab environments. This is not a broad modern-product finding from the provided evidence, but unauthenticated daemon exposure can create serious compromise risk.

Technical view

The cited CVE describes an insecure default in the boot2docker-managed Docker daemon: unauthenticated TCP connections are enabled in boot2docker 1.2 and earlier. The record does not provide CVSS, CWE, affected CPEs, exploit details, or a named patch beyond the version boundary implied by the description.

Likely exposure

Likely exposure is limited to legacy boot2docker deployments at version 1.2 or earlier where the Docker daemon TCP interface is reachable from untrusted networks. The source bundle does not identify broader Docker products, modern Docker Desktop, or specific CPEs as affected.

Exploitation context

The provided sources do not show known active exploitation, and the CVE is not listed as KEV. Risk depends on network reachability of the unauthenticated daemon interface. If reachable, the impact could include privileged control or arbitrary code execution through containers.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE, exploit status, or detailed remediation text is included in the bundle. Analysis is based on the CVE description and Docker announce reference only. Avoid expanding scope beyond boot2docker 1.2 and earlier without additional vendor evidence.

Mitigation direction

  • Inventory and retire boot2docker 1.2 and earlier installations.
  • Check Docker or boot2docker vendor guidance before applying specific fixes.
  • Remove unauthenticated Docker daemon TCP exposure from untrusted networks.
  • Restrict daemon access to trusted administrative paths only.
  • Review legacy developer laptops, CI hosts, and lab systems for old boot2docker use.

Validation and detection

  • Confirm whether any asset runs boot2docker 1.2 or earlier.
  • Verify Docker daemon TCP access is not reachable from untrusted networks.
  • Check configuration for unauthenticated daemon listeners.
  • Review historical CI and developer environment images for boot2docker usage.
  • Document any exposed legacy daemon as a high-priority remediation item.
Prepared
Confidence
medium
Sources
3

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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
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-5279 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
2Source 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.