Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Splunk Splunk Enterprise
9.0 to < 9.0affected
Splunk Splunk Cloud Platform
8.2 to < 8.2.2203affected
References
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation ↗
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates ↗
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html ↗
- 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/ ↗