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

published 2022-06-15 4y ago modified 2026-06-17 4mo ago also EUVD-2022-53389

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

Splunk Splunk Cloud Platform 8.2.2203

Is CVE-2022-32152 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	3.1	7.2	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

Splunk Splunk Enterprise
Splunk Splunk Cloud Platform

Classification

Weakness

CWE-295 Improper Certificate Validation

References

docs.splunk.com /Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
mitigation, vendor-advisory
docs.splunk.com /Documentation/Splunk/9.0.0/Security/Updates
release-notes, vendor-advisory
splunk.com /en_us/product-security/announcements/svd-2022-0602.html
vendor-advisory
research.splunk.com /application/splunk_digital_certificates_infrastructure_version/
mitigation, vendor-advisory
research.splunk.com /application/splunk_digital_certificates_lack_of_encryption/
mitigation, vendor-advisory
research.splunk.com /application/splunk_protocol_impersonation_weak_encryption_selfsigned/
mitigation, vendor-advisory
research.splunk.com /network/splunk_identified_ssl_tls_certificates/
mitigation, vendor-advisory

Sources

CVE List CVE-2022-32152
NVD CVE-2022-32152

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.