StormApplication · Apache
CVE-2018-1331
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 · uneditedIn Apache Storm 0.10.0 through 0.10.2, 1.0.0 through 1.0.6, 1.1.0 through 1.1.2, and 1.2.0 through 1.2.1, an attacker with access to a secure storm cluster in some cases could execute arbitrary code as a different user.
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 · moderate confidenceThis is a privilege escalation vulnerability in Apache Storm where an authenticated attacker with access to a secure cluster can execute arbitrary code as a different user, bypassing intended security controls.
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
> 0.10.0, <= 0.10.2>= 1.0.0, <= 1.0.6> 1.1.0, <= 1.1.2>= 1.2.0, <= 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Check Apache Storm versionRun 'storm version' command or inspect the storm-core JAR file in the installation directory for the version metadataAffected if Installed version falls within any of these ranges: >0.10.0 to <=0.10.2, >=1.0.0 to <=1.0.6, >1.1.0 to <=1.1.2, or >=1.2.0 to <=1.2.1
-
Verify if Storm security is enabledInspect the storm.yaml configuration file (typically in Storm's conf directory) and look for 'nimbus.authorizer' settingAffected if nimbus.authorizer is set to a value other than 'org.apache.storm.security.authorization.SimpleACLAuthorizer' or 'org.apache.storm.security.authorization.QuickFilterAuthorizer', indicating custom or third-party authorization is in use
-
Confirm cluster uses authenticationCheck storm.yaml for 'nimbus.authentication' and/or 'storm.authenticate' settings, or verify if a valid Kerberos keytab or authentication plugin is configuredAffected if The cluster is configured with authentication mechanisms such as Kerberos, LDAP, or custom authentication providers rather than being unsecured
-
Determine if multi-user security mode is activeLook for 'storm.messaging.transport' configuration or check if users can submit topologies or run commands as other users via 'storm kill', 'storm jar', or similar CLI operationsAffected if Multiple users have authenticated access to the cluster and can invoke operations that could be leveraged for privilege escalation
A user is affected if they run any Apache Storm version in the vulnerable ranges (0.10.1-0.10.2, 1.0.0-1.0.6, 1.1.0-1.1.2, or 1.2.0-1.2.1) on a secured cluster with authentication enabled, allowing an authenticated attacker to escalate privileges.
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 Apache Storm to version 1.2.2 or later (or corresponding patched versions for 0.10.x and 1.0.x/1.1.x branches) which contains the security fix for this vulnerability.
Fix this in Storm
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1331 — 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-1331 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