CVE-2022-32152CWE-295

Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default

High · published June 15, 2022

CVSS v3.1
8.1
EPSS
1%
Percentile
61.1
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
8.1 · HIGH
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00958 · 61.1th percentile
Weakness
CWE-295 · Improper Certificate Validation
Published
2022-06-15T16:46Z
EPSS history
Timeline
  • 15 JUN 16:46Z
    Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default
    cvelistv5