CVE-2026-40557
Full vulnerability record from the local CVENow database.
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.
View original CVE JSON
{
"id": "CVE-2026-40557",
"sourceIdentifier": "[email protected]",
"published": "2026-04-27T14:16:48.017",
"lastModified": "2026-10-26T22:10:00.163",
"vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Improper Certificate Validation via Global SSL Context Downgrade in Apache Storm Prometheus Reporter\n\n\nVersions Affected: from 2.6.3 to 2.8.6\n\n\nDescription: \n\nIn 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.\n\n\nThe 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.\n\n\n\n\nMitigation: 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."
},
{
"lang": "es",
"value": "Validación de Certificados Inapropiada a través de Degradación Global del Contexto SSL en el Reportero Prometheus de Apache Storm\n\nVersiones Afectadas: de 2.6.3 a 2.8.6\n\nDescripción:\n\nEn despliegues de producción donde un administrador habilita storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation (por defecto está deshabilitado) con la intención de afectar solo al reportero Prometheus, el efecto secundario global no documentado crea una superficie de ataque a través de cada canal de comunicación protegido por TLS en el demonio Storm.\n\nLa clase PrometheusPreparableReporter implementa un INSECURE_TRUST_MANAGER que acepta todos los certificados SSL sin validación, con métodos checkClientTrusted y checkServerTrusted vacíos. Lo más crítico, cuando la opción de configuración storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation está habilitada (por defecto = deshabilitado) para conexiones HTTPS de Prometheus PushGateway, el INSECURE_CONNECTION_FACTORY llama a SSLContext.setDefault(sslContext), lo que reemplaza globalmente el contexto SSL por defecto de la JVM en lugar de aplicar el contexto inseguro solo a la conexión de Prometheus. Esta carga útil fluye a través de la configuración de storm.yaml ? PrometheusPreparableReporter.prepare() ? INSECURE_CONNECTION_FACTORY ? SSLContext.setDefault(), resultando en una degradación de seguridad TLS a nivel de JVM. Todas las conexiones HTTPS subsiguientes en el proceso - incluyendo conexiones de ZooKeeper, Thrift, Netty y UI - confían silenciosamente en todos los certificados, incluyendo los autofirmados, caducados y generados por atacantes, habilitando la intercepción man-in-the-middle del estado del clúster, envíos de topologías, datos de tuplas y credenciales administrativas.\n\nMitigación: Los usuarios de 2.x deberían actualizar a 2.8.7 si se utiliza el Reportero de Métricas de Prometheus. Los usuarios del Reportero de Métricas de Prometheus que no puedan actualizar inmediatamente deberían eliminar la configuración storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation: true de su configuración storm.yaml y en su lugar configurar un almacén de confianza (truststore) adecuado que contenga el certificado del PushGateway."
}
],
"affected": [
{
"source": "[email protected]",
"affectedData": [
{
"vendor": "Apache Software Foundation",
"product": "Apache Storm Prometheus Reporter",
"defaultStatus": "unaffected",
"collectionURL": "https://repo.maven.apache.org/maven2/",
"packageName": "org.apache.storm:storm-metrics-prometheus",
"versions": [
{
"version": "2.6.3",
"lessThan": "2.8.7",
"versionType": "semver",
"status": "affected"
}
]
}
]
}
],
"metrics": {
"cvssMetricV31": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary",
"cvssData": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"attackVector": "NETWORK",
"attackComplexity": "HIGH",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"availabilityImpact": "NONE"
},
"exploitabilityScore": 2.2,
"impactScore": 2.5
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"timestamp": "2026-04-27T13:58:23.511144Z",
"id": "CVE-2026-40557",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"version": "2.0.3"
}
}
]
},
"weaknesses": [
{
"source": "[email protected]",
"type": "Secondary",
"description": [
{
"lang": "en",
"value": "CWE-295"
}
]
}
],
"configurations": [
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:apache:storm_prometheus_reporter:*:*:*:*:*:*:*:*",
"versionStartIncluding": "2.6.3",
"versionEndExcluding": "2.8.7",
"matchCriteriaId": "3BAEE5C8-86FE-4927-BB10-A14FFF4BFD75"
}
]
}
]
}
],
"references": [
{
"url": "https://lists.apache.org/thread/f5bv68z1y5xstz22psjk05p3wn86knjq",
"source": "[email protected]",
"tags": [
"Mailing List",
"Vendor Advisory"
]
},
{
"url": "http://www.openwall.com/lists/oss-security/2026/04/25/2",
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
]
}
]
}