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.
References
| Link | Resource |
|---|---|
| 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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: Splunk
Published: 2022-06-14T00:00:00
Updated: 2022-06-15T16:48:21
Reserved: 2022-05-31T00:00:00
Link: CVE-2022-32153
JSON object: View
NVD Information
Status : Analyzed
Published: 2022-06-15T17:15:08.950
Modified: 2022-06-24T01:22:40.257
Link: CVE-2022-32153
JSON object: View
Redhat Information
No data.