Apache Storm Client: Cross-Tenant Dependency Jar Substitution via Predictable Blob Keys
Apache Software Foundation Apache Storm Client
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software Foundation Apache Storm Client |
| No fix yet |
Original description
Description
Dependency artifacts uploaded with `storm jar --artifacts` were stored under a blob key derived only from the Maven coordinate, for example `dep---.jar`. The key was therefore identical for every user of the cluster and predictable in advance. When the blob already existed, the uploader caught `KeyAlreadyExistsException` and silently reused it, with no check that the existing blob's content or owner matched the artifact the submitter had resolved.
A user who uploaded a blob under such a key first therefore controlled the bytes that every later submitter of the same coordinate would receive on the worker classpath, resulting in code execution inside another tenant's topology.
This affects deployments where more than one principal may create blobs and where the `--artifacts` dependency feature is used.