CVE-2022-32153 Splunk Enterprise lacked TLS host name validation

High 8.1 Published Updated

Attackers with admin credentials can bypass TLS validation in Splunk-to-Splunk communications by adding peers with invalid certificates.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2022-32153?

CVE-2022-32153 is a high-severity vulnerability in Splunk Splunk, published on 15 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-295, CWE-297

Which versions are affected by CVE-2022-32153?

It affects 2 products.

Products include Splunk Splunk, Splunk Splunk Cloud Platform.

How do I fix CVE-2022-32153?

No fix has been published for CVE-2022-32153 yet. Limit exposure of the affected software until one is available.

Is CVE-2022-32153 being exploited?

There is no known exploitation of CVE-2022-32153 in the wild and no public exploit code.

All Splunk Splunk vulnerabilities

Sources

Also known as GHSA-3vq3-mvhh-hjcp.

Is CVE-2022-32153 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free