CVE-2022-32151
Summary
| CVE | CVE-2022-32151 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-06-15 17:15:00 UTC |
| Updated | 2022-06-24 01:24:00 UTC |
| 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, 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. |
Risk And Classification
Problem Types: CWE-295
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Splunk | Splunk | All | All | All | All |
| Application | Splunk | Splunk Cloud Platform | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Splunk protocol impersonation weak encryption simplerequest - Splunk Security Content | CONFIRM | research.splunk.com | |
| Configure TLS certificate host name validation - Splunk Documentation | CONFIRM | docs.splunk.com | |
| SVD-2022-0601 | Splunk | CONFIRM | www.splunk.com | |
| Security updates - Splunk Documentation | CONFIRM | docs.splunk.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
LEGACY: Chris Green at Splunk
There are currently no legacy QID mappings associated with this CVE.