Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
4<8.2.2203+ 1 more
- (no CPE)range: <8.2.2203
- (no CPE)range: 8.2
<9.0+ 1 more
- (no CPE)range: <9.0
- (no CPE)range: 9.0
Patches
Vulnerability mechanics
References
7- docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidationmitrex_refsource_CONFIRM
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updatesmitrex_refsource_CONFIRM
- research.splunk.com/application/splunk_digital_certificates_infrastructure_version/mitrex_refsource_CONFIRM
- research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/mitrex_refsource_CONFIRM
- research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/mitrex_refsource_CONFIRM
- research.splunk.com/network/splunk_identified_ssl_tls_certificates/mitrex_refsource_CONFIRM
- www.splunk.com/en_us/product-security/announcements/svd-2022-0602.htmlmitrex_refsource_CONFIRM
News mentions
0No linked articles in our index yet.