First published: Wed Jun 15 2022(Updated: )
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.
Credit: prodsec@splunk.com
Affected Software | Affected Version | How to fix |
---|---|---|
Splunk Splunk | <9.0 | |
Splunk Splunk Cloud Platform | <8.2.2203 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this issue is CVE-2022-32151.
CVE-2022-32151 has a severity rating of 9.1 (Critical).
Splunk Enterprise versions before 9.0 are affected by CVE-2022-32151.
Splunk Cloud Platform versions before 8.2.2203 are affected by 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.