Apache Storm vulnerabilities

Directory traversal vulnerability in the log viewer in Apache Storm 0.9.0.1 allows remote attackers to read arbitrary files via a .. (dot dot) in the file parameter to log.

In Apache Storm before 3.1.0, a vulnerability exists: the Netty decoder is installed before authentication and processes frames without verification, allowing an unauthenticated attacker to allocate large buffers and potentially cause memory pressure on workers.

In Apache Storm's SimpleACLAuthorizer, authorization returned early when nimbus.users was empty, skipping evaluation of nimbus.groups. As a result, a cluster restricted by group alone allowed every authenticated principal to perform all user-level operations, including submitTopology, beginFileUpload and getNimbusConf. The issue is fixed in version 3.1.0.

A vulnerability in Apache Storm allows a topology submitter to delete blobs belonging to other topologies by listing their keys in `dependency_jars` and `dependency_artifacts`. Additionally, missing validation can cause Nimbus to fail to retain leadership, rendering the cluster inoperative.

The DRPC server in Apache Storm keeps a map from function names to request queues, and entries are never removed. An attacker can send arbitrary function names without authentication (as `drpc.authorizer` is disabled by default), leading to unbounded memory growth and eventual heap exhaustion.

The UI daemon in Apache Storm 0.10.0 before 0.10.0-beta1 allows remote attackers to execute arbitrary code via unspecified vectors.

Three separate mechanisms in Apache Storm's HTTP components allowed a web page on an unrelated origin to read responses served to an authenticated user. The Logviewer reflected the request's Origin header in Access-Control-Allow-Origin while also sending Access-Control-Allow-Credentials: true, the shared CORS filter was misconfigured (a response header name was supplied where an initialisation parameter name was expected, so the container applied its own credential-allowing defaults), and the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET request. In each case, a page visited by an authenticated operator can read cluster, topology and log data on their behalf.

When ZooKeeper authentication is configured, Storm deliberately retains storm.zookeeper.topology.auth.payload in the topology configuration, and Nimbus serves that configuration to any caller with read-only topology permissions. A user granted only topology view access receives the ZooKeeper credential, which is write-capable and allows forging or removing topology state. The credential also reaches logs (INFO in the submission client, DEBUG in SASL handlers), and version 3.1.0 removes it from the served configuration and logs.

In Apache Storm before 3.1.0, the getNimbusConf function returns full configuration without redaction, and the UI endpoint /api/v1/cluster/configuration lacks proper authorization, potentially exposing passwords and keys.

In Apache Storm before 3.1.0, the rebalance operation does not revalidate the blobstore map for permissions, and listBlobs lacks authorization checks, allowing an authorized user to access disallowed blobs and disclose metadata.

In CVE-2026-82430 in Apache Storm, the setuid-root `worker-launcher` first changes ownership of the entire worker directory to the untrusted topology user and only afterwards reads the command file written into that directory. The file is opened without `O_NOFOLLOW` and without re-verifying its owner, so the tenant can replace its contents in the window between the ownership change and the read. On the Docker path the rewritten command is executed with real uid 0, and on the OCI path arbitrary host paths can be bind-mounted read-write into the container.

A time-of-check-time-of-use (TOCTOU) vulnerability exists in the setuid-root worker-launcher binary in Apache Storm. While walking worker directory trees, it calls lchown and chmod on full pathnames that are re-resolved after FTS classification. A malicious topology user can replace an intermediate directory with a symbolic link and redirect the privileged operation to an arbitrary file on the host.

This vulnerability in Apache Storm affects the `storm jar --artifacts` feature, where dependency artifacts are stored under a blob key derived solely from the Maven coordinate, making it predictable and shared across all users. If the blob already exists, it is silently reused without owner verification, allowing an attacker to control the data that other submitters receive, leading to code execution in another tenant's topology.

A vulnerability in Apache Storm allows an attacker to use relative path segments (../) in the `topology.blobstore.map` to force deletion and symlink creation at arbitrary locations, acting as the supervisor user. This can lead to recursive deletion of data and replacement of symlinks, which when workers are launched enables execution of attacker-chosen code as another tenant's OS user, breaking isolation.

A vulnerability in Apache Storm allows an authenticated user with topology submission rights to specify any server-side path as the topology jar, bypassing the intended file upload flow. Nimbus opens the path without verifying it was uploaded, enabling access to files readable by the Nimbus daemon user.

Vulnerability in Apache Storm allows unauthorized users to read credential data (e.g., storm.zookeeper.auth.payload, keystore/truststore passwords) via the topology API, because Nimbus daemon configuration is merged with topology configuration and returned without redaction.

Apache Storm up to 2.8.7, when TLS is enabled without requiring client certificate authentication, assigns a fallback principal CN=ANONYMOUS if no certificate is presented or verification fails. The SSLPeerUnverifiedException is caught and suppressed rather than rejecting the connection, resulting in fail-open behavior.

The vulnerability in Apache Storm Prometheus Reporter involves improper certificate validation. When an administrator enables storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation, the PrometheusPreparableReporter class calls SSLContext.setDefault(), globally replacing the JVM's default SSL context and causing all TLS connections in the process to trust any certificate.

A Stored Cross-Site Scripting (XSS) vulnerability in Apache Storm UI allows topology metadata (component IDs, stream names, grouping values) to be interpolated into HTML without sanitization via parseNode() and parseEdge(). An authenticated user with topology submission rights can craft a topology containing malicious HTML/JavaScript in component identifiers, which is then executed in an operator's or administrator's browser.