First published: Wed Jun 15 2022(Updated: )
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.
Credit: prodsec@splunk.com
Affected Software | Affected Version | How to fix |
---|---|---|
Splunk Splunk | <9.0 | |
Splunk Splunk Cloud Platform | <8.2.2203 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this vulnerability is CVE-2022-32153.
The severity of CVE-2022-32153 is high with a severity value of 8.1.
Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 are affected.
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.
To fix this vulnerability, upgrade Splunk Enterprise to version 9.0 or newer and Splunk Cloud Platform to version 8.2.2203 or newer.