CVE-2022-32153: Splunk Enterprise lacked TLS host name validation
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 Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2022-32153.
What is the severity of CVE-2022-32153?
The severity of CVE-2022-32153 is high with a severity value of 8.1.
Which software versions are affected by this vulnerability?
Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 are affected.
What is the impact of CVE-2022-32153?
The impact of CVE-2022-32153 is that Splunk Enterprise peers may not validate TLS certificates during Splunk-to-Splunk communications, potentially exposing sensitive information.
How can I fix this vulnerability?
To fix this vulnerability, upgrade Splunk Enterprise to version 9.0 or newer and Splunk Cloud Platform to version 8.2.2203 or newer.