CVE-2022-32152 Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default
HighCVSS 7.2
EPSS 0.85%
- Published
- Updated
- Exploit status
- No public exploit known
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.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Splunk Enterprise | >= 9.0, < 9.0 | 9.0 |
| Splunk Cloud Platform | >= 8.2, < 8.2.2203 | 8.2.2203 |
| splunk | < 9.0 | 9.0 |
| Splunk Cloud Platform | < 8.2.2203 | 8.2.2203 |
References
- docs.splunk.com mitigation vendor-advisory
- docs.splunk.com release-notes vendor-advisory
- www.splunk.com vendor-advisory
- research.splunk.com mitigation vendor-advisory
- research.splunk.com mitigation vendor-advisory
- research.splunk.com mitigation vendor-advisory
- research.splunk.com mitigation vendor-advisory