CVE-2022-32153

Splunk Enterprise lacked TLS host name validation

State
Published
Severity
8.1 High
Published
Jun 15, 2022
Updated
Sep 16, 2024
Reserved
May 31, 2022

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.18.1 HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HSplunk

Weaknesses

  • CWE-297 Improper Validation of Certificate with Host Mismatch

Affected Products

ProductVersions
Splunk EnterpriseSplunk, Inc
  • 9.0 to before 9.0Affected
Splunk Cloud PlatformSplunk, Inc
  • 8.2 to before 8.2.2203Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.