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…
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.9% (FIRST EPSS); higher than 92.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: docker.io (Debian:12) 1.3.3~dfsg1-1; github.com/docker/docker (Go) 1.3.3; docker-stable (openSUSE:Leap 15.6) 24.0.9_ce-150000.1.25.1.
Low priority for now. Upgrade to docker.io (Debian:12) 1.3.3~dfsg1-1; github.com/docker/docker (Go) 1.3.3; docker-stable (openSUSE:Leap 15.6) 24.0.9_ce-150000.1.25.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 2, 2019
- Updated
- Jun 16, 2026
- EPSS
- 4.9% · 92th percentile
- CWE
- CWE-22
Report tools
Action score
35
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| docker | docker | cpe:2.3:a:docker:docker |
Using docker? Add it to your stack and be the first to know about CVEs like this one. (Docker)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- docker dockerbefore 1.3.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | docker.io | before 1.3.3~dfsg1-1 | 1.3.3~dfsg1-1 |
| Go | github.com/docker/docker | before 1.3.3 | 1.3.3 |
| openSUSE:Leap 15.6 | docker-stable | before 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 |
| openSUSE:Tumbleweed | docker | before 1.12.3-4.1 | 1.12.3-4.1 |
| openSUSE:Tumbleweed | docker-stable | before 24.0.9_ce-15.1 | 24.0.9_ce-15.1 |
| Red Hat:rhel_extras_other:7 | docker | before 0:1.4.1-37.el7 | 0:1.4.1-37.el7 |
| Red Hat:rhel_extras_other:7 | docker-logrotate | before 0:1.4.1-37.el7 | 0:1.4.1-37.el7 |
| Red Hat:rhel_extras_other:7 | docker-python | before 0:0.7.1-37.el7 | 0:0.7.1-37.el7 |
| Red Hat:rhel_extras_other:7 | python-websocket-client | before 0:0.14.1-37.el7 | 0:0.14.1-37.el7 |
| SUSE:Linux Enterprise Module for Containers 15 SP6 | docker-stable | before 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | docker-stable | before 24.0.9_ce-1.20.1 | 24.0.9_ce-1.20.1 |
Same product
docker: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15752Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse…KEV76This week
- CVE-2019-5736runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and…64This week
- CVE-2019-14271In Docker 19.03.x before 19.03.1 linked against the GNU C Library (aka glibc), code injection can occur when the nsswitch facility…45Plan
Published before and after this one in the same product
- ← EarlierCVE-2019-13139Aug 22, 2019 · In Docker before 18.09.4, an attacker who is capable of supplying or manipulating the build path for the "docker build" command would be…34Monitor
- ← EarlierCVE-2019-16884Sep 25, 2019 · runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because…31Monitor
- Later →CVE-2014-0048Jan 2, 2020 · An issue was found in Docker before 1.6.0.41Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:docker.io | 1.3.3~dfsg1-1 · Debian:12 | Package registry (OSV) |
| Go:github.com/docker/docker | 1.3.3 | Package registry (OSV) |
| opensuse:docker | 1.12.3-4.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:docker-stable | 24.0.9_ce-150000.1.25.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:docker | 0:1.4.1-37.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-logrotate | 0:1.4.1-37.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:docker-python | 0:0.7.1-37.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| red hat:python-websocket-client | 0:0.14.1-37.el7 · Red Hat:rhel_extras_other:7 | Package registry (OSV) |
| suse:docker-stable | 24.0.9_ce-1.20.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:docker-stable | 24.0.9_ce-150000.1.25.1 · SUSE:Linux Enterprise Module for Containers 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.