vulnerability
Splunk: CVE-2022-32152: Splunk Enterprise lacked TLS certificate validation for Splunk-to-Splunk communication by default
| Severity | CVSS | Published | Added | Modified |
|---|---|---|---|---|
| 7 | (AV:N/AC:L/Au:S/C:P/I:P/A:P) | Jun 14, 2022 | Apr 7, 2025 | Oct 8, 2025 |
Severity
7
CVSS
(AV:N/AC:L/Au:S/C:P/I:P/A:P)
Published
Jun 14, 2022
Added
Apr 7, 2025
Modified
Oct 8, 2025
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 administrator 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 or higher andConfigure TLS host validation for Splunk-to-Splunk communicationsto enable the remediation. At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties.
Solution
splunk-upgrade-latest
NEW
Explore Exposure Command
Confidently identify and prioritize exposures from endpoint to cloud with full attack surface visibility and threat-aware risk context.