CVE-2026-40557 Apache Storm Prometheus Reporter: Disabling TLS verification for Prometheus Reporter also disables it for all other connections
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: partial
Description
Improper Certificate Validation via Global SSL Context Downgrade in Apache Storm Prometheus Reporter
Versions Affected: from 2.6.3 to 2.8.6
Description:
In production deployments where an administrator enables storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation (by default it is disabled) intending to affect only the Prometheus reporter, the undocumented global side effect creates an attack surface across every TLS-protected communication channel in the Storm daemon.
The PrometheusPreparableReporter class implements an INSECURE_TRUST_MANAGER that accepts all SSL certificates without validation, with empty checkClientTrusted and checkServerTrusted methods. Most critically, when the storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation configuration option is enabled (default = disabled) for HTTPS Prometheus PushGateway connections, the INSECURE_CONNECTION_FACTORY calls SSLContext.setDefault(sslContext), which globally replaces the JVM's default SSL context rather than applying the insecure context only to the Prometheus connection. This payload flows through storm.yaml configuration → PrometheusPreparableReporter.prepare() → INSECURE_CONNECTION_FACTORY → SSLContext.setDefault(), resulting in a JVM-wide TLS security downgrade. All subsequent HTTPS connections in the process - including ZooKeeper, Thrift, Netty, and UI connections - silently trust all certificates, including self-signed, expired, and attacker-generated ones, enabling man-in-the-middle interception of cluster state, topology submissions, tuple data, and administrative credentials.
Mitigation: 2.x users should upgrade to 2.8.7 if the Prometheus Metrics Reporter is used. Prometheus Metrics Reporter Users who cannot upgrade immediately should remove the storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation: true setting from their storm.yaml configuration and instead configure a proper truststore containing the PushGateway's certificate.
Upgrade path
2 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| apache storm prometheus reporter | >= 2.6.3, < 2.8.7 | 2.8.7 | Fixed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.6.3; = 2.6.4; = 2.7.0; = 2.7.1 +8 more | 2.8.7 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| org.apache.storm/storm-metrics-prometheus(Maven) | >= 2.6.3, < 2.8.7 | 2.8.7 |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.6.3 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.6.4 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.7.0 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.7.1 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.8.0 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.8.1 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.8.2 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.8.3 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.8.4 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.8.5 | No fix listed |
| org.apache.storm/storm-metrics-prometheus(Maven) | = 2.8.6 | No fix listed |
| apache storm prometheus reporter | >= 2.6.3, < 2.8.7 | 2.8.7 |
References
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com product
- lists.apache.org mailing-list vendor-advisory
- www.openwall.com mailing-list third-party-advisory
- github.com