Vulnerability record · CVE-2022-32151 · published 15 June 2022
CVE-2022-32151: Splunk improper certificate validation vulnerability
Splunk · Splunk
The httplib and urllib Python libraries that Splunk shipped with Splunk Enterprise did not validate certificates using the certificate authority (CA) certificate stores by default in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203. Python 3 client libraries now verify server certificates by default and use the appropriate CA certificate stores for each library. Apps and add-ons that include their own HTTP libraries are not affected. 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.
Description
The httplib and urllib Python libraries that Splunk shipped with Splunk Enterprise did not validate certificates using the certificate authority (CA) certificate stores by default in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203. Python 3 client libraries now verify server certificates by default and use the appropriate CA certificate stores for each library. Apps and add-ons that include their own HTTP libraries are not affected. 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation | Vendor Advisory |
| https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates | Release NotesVendor Advisory |
| https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplerequest/ | MitigationVendor Advisory |
| https://www.splunk.com/en_us/product-security/announcements/svd-2022-0601.html | Vendor Advisory |
| https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation | Vendor Advisory |
| https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates | Release NotesVendor Advisory |
| https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplerequest/ | MitigationVendor Advisory |
| https://www.splunk.com/en_us/product-security/announcements/svd-2022-0601.html | Vendor Advisory |
Track CVE-2022-32151 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2022-32151), CISA KEV, FIRST EPSS (scores of 2026-10-05). This page is refreshed as NVD updates the record.
