StormApplication · Apache
CVE-2019-0202
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 · uneditedThe Apache Storm Logviewer daemon exposes HTTP-accessible endpoints to read/search log files on hosts running Storm. In Apache Storm versions 0.9.1-incubating to 1.2.2, it is possible to read files off the host's file system that were not intended to be accessible via these endpoints.
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 confidenceThe Apache Storm Logviewer daemon contains a path traversal vulnerability in its HTTP-accessible endpoints that allows unauthorized reading of arbitrary files from the host filesystem beyond the intended log directory scope, enabling attackers to access sensitive system files.
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.9.3, <= 1.2.2= 0.9.1= 0.9.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify Apache Storm installation and versionLocate the Storm installation directory and check the version file or run 'storm version' command if Storm is in PATH. Common locations include /opt/apache-storm, /usr/local/storm, or a user-installed directory. Compare the version against the affected range: 0.9.1 through 1.2.2.Affected if The installed version falls within 0.9.1 to 1.2.2 inclusive
-
Verify if the logviewer daemon is enabled or runningCheck for the logviewer process or service. This may appear as 'logviewer' in process listings (ps aux), or as a configured component in Storm's conf/ directory. Inspect the logviewer configuration file if one exists in the Storm distribution.Affected if The logviewer daemon is running or is configured to run
-
Confirm HTTP accessibility of logviewerDetermine if the logviewer HTTP endpoint is accessible. This typically listens on port 8000 or 8080. Check firewall rules, bind addresses in configuration, and whether the logviewer process is bound to an interface accessible to potential attackers.Affected if The logviewer HTTP port is reachable from untrusted networks or allows unauthenticated access
A user is affected if running Apache Storm version 0.9.1-1.2.2 with the logviewer daemon enabled and its HTTP interface accessible, as this combination allows path traversal exploitation.
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.3 or later where the vulnerability is patched, or disable the logviewer daemon if not required in production environments.
Fix this in Storm
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0202 — 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-2019-0202 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