CVE-2022-32152: Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default
First published: Wed Jun 15 2022(Updated: )
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.
Credit: prodsec@splunk.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Splunk Splunk | <9.0 | |
| Splunk Splunk Cloud Platform | <8.2.2203 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
- 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/
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2022-32152.
What is the severity of CVE-2022-32152?
The severity of CVE-2022-32152 is high with a severity value of 7.2.
Which software versions are affected by CVE-2022-32152?
Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 are affected by CVE-2022-32152.
What is the impact of CVE-2022-32152?
CVE-2022-32152 allows MITM (Man-in-the-Middle) attackers to obtain sensitive information, modify data, or impersonate trusted peers.
How can I fix CVE-2022-32152?
To fix CVE-2022-32152, ensure that Splunk peer communications are configured properly with valid TLS certificates and enable TLS certificate hostname validation.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/weakness
- agent/last-modified-date
- agent/references
- agent/title
- agent/description
- agent/first-publish-date
- agent/event
- agent/tags
- vendor/splunk
- canonical/splunk splunk
- canonical/splunk splunk cloud platform