CVSS: 8.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-32153 – Splunk Enterprise lacked TLS host name validation
https://notcve.org/view.php?id=CVE-2022-32153
Splunk Enterprise peers in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 did not validate the TLS certificates during Splunk-to-Splunk communications by default. Splunk peer communications configured properly with valid certificates were not vulnerable. However, an attacker with administrator credentials could add a peer without a valid certificate and connections from misconfigured nodes without valid certificates did not fail by default. 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. Los peers de Splunk Enterprise en las versiones de Splunk Enterprise anteriores a la 9.0 y las versiones de Splunk Cloud Platform anteriores a la 8.2.2203 no comprueban los certificados TLS durante las comunicaciones de Splunk a Splunk por defecto. • https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned https://research.splunk.com/network/splunk_identified_ssl_tls_certificates https://www.splunk.com/en_ • CWE-295: Improper Certificate Validation CWE-297: Improper Validation of Certificate with Host Mismatch •
CVSS: 8.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-32152 – Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default
https://notcve.org/view.php?id=CVE-2022-32152
Splunk Enterprise peers in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 did not validate the TLS certificates during Splunk-to-Splunk communications by default. Splunk peer communications configured properly with valid certificates were not vulnerable. However, an attacker with administrator credentials could add a peer without a valid certificate and connections from misconfigured nodes without valid certificates did not fail by default. 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. Los peers de Splunk Enterprise en Splunk Enterprise versiones anteriores a 9.0 y Splunk Cloud Platform versiones anteriores a 8.2.2203 no comprueban los certificados TLS durante las comunicaciones de Splunk a Splunk por defecto. • https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned https://research.splunk.com/network/splunk_identified_ssl_tls_certificates https://www.splunk.com/en_ • CWE-295: Improper Certificate Validation •
CVSS: 9.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-32151 – Splunk Enterprise disabled TLS validation using the CA certificate stores in Python 3 libraries by default
https://notcve.org/view.php?id=CVE-2022-32151
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. Las bibliotecas de Python httplib y urllib que Splunk envió con Splunk Enterprise no comprueban los certificados usando los almacenes de certificados de la autoridad de certificación (CA) de forma predeterminada en Splunk Enterprise versiones anteriores a 9.0 y Splunk Cloud Platform versiones anteriores a 8.2.2203. • https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplerequest https://www.splunk.com/en_us/product-security/announcements/svd-2022-0601.html • CWE-295: Improper Certificate Validation •
CVSS: 8.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-32156 – Splunk Enterprise and Universal Forwarder CLI connections lacked TLS cert validation
https://notcve.org/view.php?id=CVE-2022-32156
In Splunk Enterprise and Universal Forwarder versions before 9.0, the Splunk command-line interface (CLI) did not validate TLS certificates while connecting to a remote Splunk platform instance by default. After updating to version 9.0, see Configure TLS host name validation for the Splunk CLI https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI to enable the remediation. The vulnerability does not affect the Splunk Cloud Platform. At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties. The issue requires conditions beyond the control of a potential bad actor such as a machine-in-the-middle attack. Hence, Splunk rates the complexity of the attack as High. • https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.html • CWE-295: Improper Certificate Validation •
CVSS: 8.8EPSS: 0%CPEs: 1EXPL: 0CVE-2022-27183 – Reflected XSS in a query parameter of the Monitoring Console
https://notcve.org/view.php?id=CVE-2022-27183
The Monitoring Console app configured in Distributed mode allows for a Reflected XSS in a query parameter in Splunk Enterprise versions before 8.1.4. The Monitoring Console app is a bundled app included in Splunk Enterprise, not for download on SplunkBase, and not installed on Splunk Cloud Platform instances. Note that the Cloud Monitoring Console is not impacted. La aplicación de la Consola de Monitorización configurada en modo Distribuido permite un ataque de tipo XSS Reflejado en un parámetro de consulta en las versiones de Splunk Enterprise anteriores a la 8.1.4. La aplicación de la Consola de Monitoreo es una aplicación incluida en Splunk Enterprise, no puede descargarse en SplunkBase, y no es instalada en las instancias de Splunk Cloud Platform. • https://research.splunk.com/application/splunk_xss_in_monitoring_console https://www.splunk.com/en_us/product-security/announcements/svd-2022-0505.html • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •