cve.bz

CVE-2014-6407 docker docker: Link Following

no score yetEPSS 5.2%Fix available

docker docker: no CVSS score yet. EPSS 5.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/docker/docker 1.3.2.

On this page
Docker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a (1) symlink or (2) hard link attack in an image archive in a (a) pull or (b) load operation.
EPSS
5.2% (unchanged from 4.9% a week ago; 4.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 93rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2014-6407 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2014-6407?via=ask-ai-copy and https://cve.bz/cve/CVE-2014-6407?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2014-6407 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
docker:dockerthrough 1.3.1
docker:docker1.0.0
docker:docker1.3.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5qgp-p5jc-w2rmGogithub.com/docker/docker<1.3.21.3.2
GO-2022-0630Gogithub.com/docker/docker<1.3.21.3.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14docker.io1.3.2~dfsg1-1DEBIAN-CVE-2014-6407
Red Hatrhel_extras_other:7docker0:1.3.2-4.el7RHBA-2014:1977
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 11 moredocker-stable24.0.9_ce-150000.1.25.1SUSE-SU-2025:03545-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5docker-stable24.0.9_ce-1.20.1SUSE-SU-2025:03540-1
openSUSELeap 15.6docker-stable24.0.9_ce-150000.1.25.1SUSE-SU-2025:03545-1
openSUSETumbleweeddocker1.12.3-4.1openSUSE-SU-2024:10532-1
openSUSETumbleweeddocker-stable24.0.9_ce-15.1openSUSE-SU-2025:15589-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Red Hat · SUSE · openSUSE.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This issue affects the versions of Docker as shipped with Red Hat Enterprise Linux 7. However, this flaw is not known to be exploitable under any supported scenario. A future update may address this issue.

Red Hat does not support or recommend running untrusted images.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 7 Extrasdocker-0:1.3.2-4.el7Fixed 2014-12-10RHBA-2014:1977

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2014-6407.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON