CVE-2022-32156

published 14 Jun 2022 · updated 2 Nov 2026

Splunk Enterprise and Universal Forwarder CLI connections lacked TLS cert validation

7.4HighCVSS 7.4EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Enterprise 9.0.0, Universal Forwarder 9.0, Universal Forwarder 9.0.0 and 1 more.

In Splunk Enterprise and Universal Forwarder versions before 9.0, the Splunk command-line interface (CLI) did not validate TLS certificates while connecting to a remote Splunk platform instance by default. After updating to version 9.0, see Configure TLS host name validation for the Splunk CLI https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI to enable the remediation. The vulnerability does not affect the Splunk Cloud Platform. At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties. The issue requires conditions beyond the control of a potential bad actor such as a machine-in-the-middle attack. Hence, Splunk rates the complexity of the attack as High.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
SplunkEnterprise<9.0.09.0.0
SplunkUniversal Forwarder<9.0, <9.0.09.0, 9.0.0
Splunksplunk<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-32156 severity on Zeptric[![CVE-2022-32156](https://zeptric.io/badge/cve/CVE-2022-32156.svg)](https://zeptric.io/cve/CVE-2022-32156)