CVE-2022-32151
Last modified
CVE-2022-32151 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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. EPSS estimates a 0.73% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk | < 9.0 |
| Splunk | Splunk Cloud Platform | < 8.2.2203 |
References
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesRelease Notes, Vendor Advisory
- https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplerequest/Mitigation, Vendor Advisory
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesRelease Notes, Vendor Advisory
- https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplerequest/Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-32151?
How severe is CVE-2022-32151?
How do I fix CVE-2022-32151?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-32145A vulnerability has been identified in Teamcenter Active Wor…6.1
- CVE-2022-32147Rejected reason: reserved but not needed
- CVE-2022-32148Improper exposure of client IP addresses in net/http before …6.5
- CVE-2022-32149An attacker may cause a denial of service by crafting an Acc…7.5
- CVE-2022-3215NIOHTTP1 and projects using it for generating HTTP responses…7.5
- CVE-2022-32150Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2022-32152Splunk Enterprise peers in Splunk Enterprise versions before…7.2
- CVE-2022-32153Splunk Enterprise peers in Splunk Enterprise versions before…8.1
- CVE-2022-32154Dashboards in Splunk Enterprise versions before 9.0 might le…8.1
- CVE-2022-32155In universal forwarder versions before 9.0, management servi…7.5
- CVE-2022-32156In Splunk Enterprise and Universal Forwarder versions before…8.1
- CVE-2022-32157Splunk Enterprise deployment servers in versions before 9.0 …7.5
Are you affected by CVE-2022-32151?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
