Splunk Enterprise disabled TLS validation using the CA certificate stores in Python 3 libraries by default
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-295.
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Splunk | Splunk Enterprise | 9.0 to before 9.0 | 9.0 | Patch available | CNA |
| Splunk | Splunk Cloud Platform | 8.2 to before 8.2.2203 | 8.2.2203 | Patch available | CNA |
Remediation
- Fix · CNA Splunk Enterprise (Splunk, Inc) Fixed in 9.0
- Fix · CNA Splunk Cloud Platform (Splunk, Inc) Fixed in 8.2.2203
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Splunk Enterprise 9.0
4 records Highest priority Priority MEDIUM 1 MEDIUM, 3 LOW
Other records, highest priority first
- TI-2022-13886 Risky commands warnings in Splunk Enterprise DashboardsPriority LOW 38
- TI-2022-13885 Splunk Enterprise lacked TLS host name validationPriority LOW 37
- TI-2022-13889 Splunk Enterprise deployment servers allow unauthenticated forwarder bundle downloadsPriority LOW 36
- Release ·
Splunk Cloud Platform 8.2.2203
2 records Highest priority Priority MEDIUM 1 MEDIUM, 1 LOW
Other records, highest priority first
- TI-2022-13885 Splunk Enterprise lacked TLS host name validationPriority LOW 37
Timeline
- 2026-10-02 Threatist record created from CVE-2022-32151
- 2026-10-03 Alias added: GHSA-4mv8-3862-hghv
References
Advisory 4
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0601.html
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
- https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplerequest/
More Splunk vulnerabilities
- TI-2026-16444 Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise KEVCVSS 3.1CRITICAL 9.8
- TI-2014-00154 The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly… KEVCVSS 3.1HIGH 7.5
- TI-2023-24841 Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing CVSS 3.1HIGH 8.8
- TI-2023-15979 ‘edit_user’ Capability Privilege Escalation CVSS 3.1HIGH 8.8
- TI-2024-30707 Remote Code Execution (RCE) due to insecure session storage configuration in Splunk Enterprise on Windows CVSS 3.1HIGH 8.8
- TI-2022-21345 Reflected Cross-Site Scripting via the radio template in Splunk Enterprise CVSS 3.1HIGH 8.8
Sources
- CVE-2022-32151 · CVE Program
- CVE-2022-32151 · NVD
- FIRST EPSS
- GHSA-4mv8-3862-hghv · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences