# CVE-2014-9358: Directory Traversal in Docker

> Remote attackers can exploit improper image ID validation in Docker to perform path traversal and spoof repositories via crafted images.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-9358, GHSA-qmmc-jppf-32wv, GO-2022-0705

## What is CVE-2014-9358?

CVE-2014-9358 is a medium-severity path traversal vulnerability in n/a, published on 16 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-9358?

3 open source packages ship an affected version, including github.com/docker/docker. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/docker/docker` | Go | All versions | 1.3.2 |
| `github.com/docker/docker` | Go | All versions | 1.3.2 |
| `github.com/docker/docker` | Go | All versions | 1.3.2 |

Products: Docker Docker.

## How do I fix CVE-2014-9358?

Upgrade github.com/docker/docker to 1.3.2 or later.

## Is CVE-2014-9358 being exploited?

There is no known exploitation of CVE-2014-9358 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-9357](https://insights.sbomify.com/CVE-2014-9357/): Arbitrary Code Execution (critical 10.0)
- [CVE-2020-14298](https://insights.sbomify.com/CVE-2020-14298/): Privilege escalation in Docker (high 8.8)
- [CVE-2020-14300](https://insights.sbomify.com/CVE-2020-14300/): Privilege escalation in Docker (high 8.8)
- [CVE-2018-15514](https://insights.sbomify.com/CVE-2018-15514/): Deserialization in n/a (high 8.8)
- [CVE-2014-9356](https://insights.sbomify.com/CVE-2014-9356/): Path Traversal in Docker (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9358 and fix it if it is affected.

What it is: CVE-2014-9358 is a medium-severity path traversal vulnerability in n/a, published on 16 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9358 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/docker/docker (Go): affected all versions; fixed in 1.3.2
- github.com/docker/docker (Go): affected all versions; fixed in 1.3.2
- github.com/docker/docker (Go): affected all versions; fixed in 1.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-9358/ (Markdown: https://insights.sbomify.com/CVE-2014-9358/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-9358
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-9358
- OSV: https://osv.dev/vulnerability/CVE-2014-9358

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-9358/
Summaries are generated and may contain mistakes; the official description above is the record.