CVE-2022-32151: Splunk Enterprise disabled TLS validation using the CA certificate stores in Python 3 libraries by default
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.
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2022-32151.
What is the severity rating of CVE-2022-32151?
CVE-2022-32151 has a severity rating of 9.1 (Critical).
Which versions of Splunk Enterprise are affected by CVE-2022-32151?
Splunk Enterprise versions before 9.0 are affected by CVE-2022-32151.
Which versions of Splunk Cloud Platform are affected by CVE-2022-32151?
Splunk Cloud Platform versions before 8.2.2203 are affected by CVE-2022-32151.
How can I fix CVE-2022-32151?
To fix CVE-2022-32151, update Splunk Enterprise to version 9.0 or later and Splunk Cloud Platform to version 8.2.2203 or later.