CVE-2022-32151 json
Splunk Enterprise disabled TLS validation using the CA certificate stores in Python 3 libraries by default
published 4y ago modified 4mo ago also EUVD-2022-53388
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Splunk, Inc Splunk Cloud Platform 8.2.2203
Is CVE-2022-32151 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
Affected products
- Splunk, Inc Splunk Enterprise
- Splunk, Inc Splunk Cloud Platform
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
splunk.com
/en_us/product-security/announcements/svd-2022-0601.html
vendor-advisory
-
docs.splunk.com
/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
vendor-advisory
-
docs.splunk.com
/Documentation/Splunk/9.0.0/Security/Updates
release-notes, vendor-advisory
-
research.splunk.com
/application/splunk_protocol_impersonation_weak_encryption_simplerequest/
mitigation, vendor-advisory
Sources
- CVE List CVE-2022-32151
- NVD CVE-2022-32151
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.