CVE-2022-32156

Plain English Summary

AI-powered analysis for quick understanding

This vulnerability allows an attacker to potentially intercept and manipulate data between the Splunk command-line interface and a remote Splunk instance because the system does not verify the security of the connection by default. However, for this to happen, the attacker would need to be in a position to perform a man-in-the-middle attack, which requires specific conditions that are not easily achievable.

Technical Description

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.

CVSS Vector Analysis

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
Confidentiality ImpactHigh
Integrity ImpactHigh
Availability ImpactHigh
ScopeUnchanged

Vector String

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploit Resources

Search for proof-of-concept code and exploit modules

Official References

Est. Bounty
$3,316($1K-$5K)
Vendor Response
Grade FPatched in 1350 days

Quick Information

Published

Jun 15, 2022

almost 4 years ago

Last Modified

Feb 25, 2026

about 1 month ago

Vendor

splunk

Product

splunk