StormApplication · Apache
CVE-2018-8008
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApache 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Storm versions 1.0.6 and earlier, 1.2.1 and earlier, and 1.1.2 and earlier contain a path traversal vulnerability in their archive extraction functionality. When processing uploaded archives (zip, bzip2, tar, xz, war, cpio, 7z), the application fails to sanitize filenames containing '..' sequences, allowing attackers to write files to arbitrary locations on the filesystem outside the intended target directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
StormApplication
<= 1.0.6<= 1.1.2<= 1.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Apache Storm versionRun 'storm version' command or check the storm-core jar manifest, typically found in the lib directory of the Storm installationAffected if The version number is 1.0.6 or lower, 1.1.2 or lower, or 1.2.1 or lower
-
Identify if Nimbus topology submission is accessibleReview cluster configuration and network access controls for the Nimbus service (typically port 6627). Check if untrusted or unauthenticated users can submit Storm topologiesAffected if Untrusted users can submit topologies to the Storm cluster, which triggers archive extraction during topology packaging
-
Check for archive-based topology artifactsExamine any uploaded topologies for presence of archives (zip, bzip2, tar, xz, war, cpio, 7z) in the topology package. These archives are extracted during topology submission processAffected if Topologies containing compressed archives are being processed by the Storm cluster
-
Verify archive extraction directory isolationInspect the extraction behavior of the archive handler. Look for evidence that filenames containing '..' sequences could be written outside the intended worker directoryAffected if Archive extraction does not sanitize '..' sequences in filenames, allowing path traversal outside the worker directory
A user is affected if they run Apache Storm version 1.0.6 or earlier, 1.1.2 or earlier, or 1.2.1 or earlier AND untrusted users can submit topologies containing archive files that get extracted by the Storm cluster.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Apache Storm version 1.0.7, 1.2.2, or 1.1.3 or later. Until patching is possible, avoid processing untrusted archive files through the affected functionality.
Fix this in Storm
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-8008 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data