CVE-2018-8008 is a medium-severity (CVSS 5.5) Path Traversal vulnerability in org.apache.storm:storm-core. A fix is available for org.apache.storm:storm-core — see the affected versions and patch details below.
ZipSlip in org.apache.storm:storm-core
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.storm:storm-core☕org.apache.storm:storm-core☕org.apache.storm:storm-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Apache Storm version 1.0.6 and earlier, 1.2.1 and earlier, and version 1.1.2 and earlier expose an arbitrary file write vulnerability, that can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar, xz, war, cpio, 7z), that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.storm:storm-core | ≥ 1.1.0&&< 1.1.3 | 1.1.3org.apache.storm:storm-core:1.1.3 |
| ☕Maven | org.apache.storm:storm-core | ≥ 1.2.0&&< 1.2.2 | 1.2.2org.apache.storm:storm-core:1.2.2 |
| ☕Maven | org.apache.storm:storm-core | all versions | 1.0.7org.apache.storm:storm-core:1.0.7 |
Affected Products
stormapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.storm:storm-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.storm:storm-core to 1.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-8008 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2018-8008 in your dependencies?
Find it across Maven, including transitive dependencies.