Vulnerabilities · 2022 · Splunk
CVE-2022-32151
Splunk vulnerability
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 products
Splunk, Splunk Cloud Platform. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Splunk runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation · Vendor Advisory
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates · Vendor Advisory
- research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplereques · Mitigation
- www.splunk.com/en_us/product-security/announcements/svd-2022-0601.html · Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-32151
- cve.org/CVERecord?id=CVE-2022-32151
More vulnerabilities in Splunk products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.