CVE-2022-32152

published 15 Jun 2022 · updated 17 Sep 2024

Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default

8.1HighCVSS 8.1EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Cloud Platform 8.2.2203 and Enterprise 9.0.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
SplunkCloud Platform>=8.2 <8.2.22038.2.2203
SplunkEnterprise>=9.0 <9.09.0

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Enterprise, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-32152 severity on Zeptric[![CVE-2022-32152](https://zeptric.io/badge/cve/CVE-2022-32152.svg)](https://zeptric.io/cve/CVE-2022-32152)