Splunk Enterprise disabled TLS validation using the CA certificate stores in Python 3 libraries by default

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

Severity Considerations

By default, Splunk Enterprise is not impacted. The vulnerability requires an app using the httplib or urllib Python library not to use TLS verification. If no apps are misconfigured, updating to 9.0 and enabling the change only remediates the potential for impact or the potential for a vulnerability. It does not remediate any currently present vulnerability. If so, the vulnerability is informational.

The severity assumes the information sent and received is highly confidential and sensitive, such as tokens and passwords. Most app communications do not meet that qualification. If so, the severity is reduced to Medium.

Acknowledgments

Chris Green at Splunk

Detections

• Splunk protocol impersonation weak encryption simplerequest

Changelog

2022-07-18: Added Severity Considerations