CVE-2014-9358 json
Directory Traversal in Docker
published 2014-12-16 11 y ago modified 2026-09-10 1 mo ago also GHSA-qmmc-jppf-32wv , GO-2022-0705 , EUVD-2022-1156
- cvss
- 6.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2) "registry communications."
Patch / fix
- go github.com/docker/docker 1.3.2
- docker.io Debian 14, Debian 13, Debian 12 1.3.3~dfsg1-1
debian advisories DEBIAN-CVE-2014-9358
- docker RHEL 7 EXTRAS_OTHER 1.3.2-4.el7
red hat advisories RHBA-2014:1977
- docker-stable SLES for SAP 15 SP5, SLES for SAP 15 SP4, SLES for SAP 15 SP3 +12 more 24.0.9_ce-150000.1.25.1
- docker-stable SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 24.0.9_ce-1.20.1
suse advisories SUSE-SU-2025:03545-1SUSE-SU-2025:03540-1
- docker-stable openSUSE Tumbleweed 24.0.9_ce-15.1
- docker openSUSE Tumbleweed 1.12.3-4.1
opensuse advisories openSUSE-SU-2025:15589-1openSUSE-SU-2024:10532-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-9358 updated cvss 7.1
docker: Path traversal and spoofing opportunities presented through image identifiers
-
Red Hat Enterprise Linux 7 Extras docker 1.3.2-4.el7fixed: vendor fix RHBA-2014:1977
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.53% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/docker/docker | <1.3.2 |
1.3.2 |
Classification
- Weakness
- Technology feeds
References
-
groups.google.com
/forum/#%21msg/docker-user/nFAz-B-n4Bw/0wr3wvLsnUwJ
web
-
securityfocus.com
/archive/1/534215/100/0/threaded
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2014-9358
advisory
-
access.redhat.com
/security/cve/cve-2014-9358
web
-
groups.google.com
/forum/#!msg/docker-user/nFAz-B-n4Bw/0wr3wvLsnUwJ
web
-
web.nvd.nist.gov
/view/vuln/detail?vulnId=CVE-2014-9358
web
-
github.com
/advisories/GHSA-qmmc-jppf-32wv
advisory
-
groups.google.com
/g/docker-user/c/nFAz-B-n4Bw/m/0wr3wvLsnUwJ
web
Sources
- CVE List CVE-2014-9358
- GitHub Advisory GHSA-qmmc-jppf-32wv
- NVD CVE-2014-9358
- OSV GO-2022-0705
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.