CVE-2022-32152Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default
- 8.1HighCVSS base score
- 0.97%Exploitation in 30 daysEPSS · top 37% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Splunk
- 15 days later
· 15 days later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| SplunkCNA (assigner) | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.97% · top 37% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.
Affected products
- affected 9.0 – < 9.0
Splunk · Splunk Cloud Platform
- affected 8.2 – < 8.2.2203
References
References7
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/ (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/ (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/ (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/ (opens in a new tab)x_refsource_CONFIRMx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-53389 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-32152)Record last updated .