CVE-2026-40557

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