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.
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.
The product does not validate, or incorrectly validates, a certificate.
| Link | Tags |
|---|---|
| https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation | mitigation vendor advisory |
| https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates | release notes vendor advisory |
| https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/ | mitigation vendor advisory |
| https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/ | mitigation vendor advisory |
| https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/ | mitigation vendor advisory |
| https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/ | mitigation vendor advisory |
| https://www.splunk.com/en_us/product-security/announcements/svd-2022-0603.html | vendor advisory |