Splunk Enterprise disabled TLS validation using the CA certificate stores in Python 3 libraries by default
Advisory ID: SVD-2022-0601 Published: 2022-06-14 CVSSv3.1 Score: 7.4, High CWE: CWE-295 CSAF: 2022-06-14-svd-2022-0601 |
CVE ID: CVE-2022-32151 Last Update: 2022-06-14 CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Bug ID: SPL-173641, SPL-129677 Security Content: Splunk protocol impersonation weak encryption simplerequest |
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, upgrade to version 9.0 or higher and Configure TLS host name validation for Splunk Python modules to enable the remediation.
At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties.
Solution
For Splunk Enterprise, upgrade to version 9.0 or higher and Configure TLS host name validation for Splunk Python modules.
For Splunk Cloud Platform customers, Splunk is actively patching and monitoring Splunk Cloud instances.
Product Status
Product | Affected Versions |
---|---|
Splunk Enterprise | Versions before 9.0 |
Splunk Cloud Platform | Versions before 8.2.2203 |
Acknowledgments
Chris Green at Splunk