CVE-2022-32153

Splunk Enterprise lacked TLS host name validation

Published Jun 15, 2022 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed

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

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

Splunk, Inc

Splunk Enterprise

affected

Version	Status	Constraints
`9.0`	affected	< 9.0

Splunk, Inc

Splunk Cloud Platform

affected

Version	Status	Constraints
`8.2`	affected	< 8.2.2203

Configuration 1 [-]

OR	cpe:2.3:a:splunk:splunk:::::enterprise:::*
	cpe:2.3:a:splunk:splunk_cloud_platform::::::::

No data.

No data available yet.

Remediation

No solution or workaround provided in the CVE record

Tracking

Advisories

Source	ID	Title
EUVD	EUVD-2022-53390	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.

Metrics

No CVSS v4.0

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

Access Vector Network

Access Complexity Medium

Authentication None

Confidentiality Impact Partial

Integrity Impact Partial

Availability Impact Partial

This CVE is not in the KEV list.

Exploit prediction score: < 1% (0.932% probability within 30 days)

Key SSVC decision points have not yet been added.

References

Link	Providers
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-0603.html