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
Noroxi assessment
Priority: Monitor (action score 31/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 91.9% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: docker.io (Debian:12) 1.3.2~dfsg1-1; github.com/docker/docker (Go) 1.3.2; docker (openSUSE:Tumbleweed) 1.12.3-4.1.
Low priority for now. Upgrade to docker.io (Debian:12) 1.3.2~dfsg1-1; github.com/docker/docker (Go) 1.3.2; docker (openSUSE:Tumbleweed) 1.12.3-4.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
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.
- Published
- Dec 12, 2014
- Updated
- Jun 16, 2026
- EPSS
- 4.9% · 91th percentile
- CWE
- CWE-59
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 dockerup to 1.3.1 inclusive
- docker docker1.0.0
- docker docker1.3.0
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.2~dfsg1-1 | 1.3.2~dfsg1-1 |
| Go | github.com/docker/docker | before 1.3.2 | 1.3.2 |
| 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.3.2-4.el7 | 0:1.3.2-4.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 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 docker-credential-wincred.exKEV76This 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 consequen64This 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 dynamical45Plan
- CVE-2014-9357Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build in a Dockerfile in 42Plan
- CVE-2014-0048An issue was found in Docker before 1.6.0.41Plan
- CVE-2018-15514HandleRequestAsync in Docker for Windows before 18.06.0-ce-rc3-win68 (edge) and before 18.06.0-ce-win72 (stable) deserialized requests over 36Monitor
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.2~dfsg1-1 · Debian:12 | Package registry (OSV) |
| Go:github.com/docker/docker | 1.3.2 | 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.3.2-4.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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
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)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.