CVE-2022-32151: fallo de gravedad alta en Splunk Enterprise
Splunk Enterprise disabled TLS validation using the CA certificate stores in Python 3 libraries by default
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 7.4epss 0.8%
The httplib and urllib Python libraries that Splunk shipped with Splunk Enterprise did not validate certificates using the certificate authority (CA) certificate stores by default in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203. Python 3 client libraries now verify server certificates by default and use the appropriate CA certificate stores for each library. Apps and add-ons that include their own HTTP libraries are not affected. For Splunk Enterprise, update to Splunk Enterprise version 9.0 and Configure TLS host name validation for Splunk-to-Splunk communications (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation) to enable the remediation.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CVEs relacionadas — Splunk Enterprise
En el mismo producto, de las más peligrosas a las menos.
CVE-2022-32158CRITICALSplunk Enterprise deployment servers allow client publishing of forwarder bundlesEPSS 1.5%CVE-2022-32154MEDIUMRisky commands warnings in Splunk Enterprise DashboardsEPSS 1.5%CVE-2022-32157HIGHSplunk Enterprise deployment servers allow unauthenticated forwarder bundle downloadsEPSS 1.4%CVE-2022-32153HIGHSplunk Enterprise lacked TLS host name validationEPSS 0.9%
Referencias
https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidationhttps://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updateshttps://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplerequest/https://www.splunk.com/en_us/product-security/announcements/svd-2022-0601.html