CVE-2022-32153

Splunk Enterprise peers in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 did not validate the TLS certificates during Splunk-to-Splunk communications by default. Splunk peer communications configured properly with valid certificates were not vulnerable. However, an attacker with administrator credentials could add a peer without a valid certificate and connections from misconfigured nodes without valid certificates did not fail by default. 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.

• CWE-297
• CWE-295

• https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidationMitigation, Vendor Advisory
• https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesRelease Notes, Vendor Advisory
• https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/Mitigation, Vendor Advisory
• https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/Mitigation, Vendor Advisory
• https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/Mitigation, Vendor Advisory
• https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/Mitigation, Vendor Advisory
• https://www.splunk.com/en_us/product-security/announcements/svd-2022-0603.htmlVendor Advisory
• https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidationMitigation, Vendor Advisory
• https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesRelease Notes, Vendor Advisory
• https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/Mitigation, Vendor Advisory
• https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/Mitigation, Vendor Advisory
• https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/Mitigation, Vendor Advisory
• https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/Mitigation, Vendor Advisory
• https://www.splunk.com/en_us/product-security/announcements/svd-2022-0603.htmlVendor Advisory

Published

Jun 15, 2022

Last Modified

Jun 17, 2026

Status

Modified

• 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.

• 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-32151The httplib and urllib Python libraries that Splunk shipped …9.1
• CVE-2022-32152Splunk Enterprise peers in Splunk Enterprise versions before…7.2
• 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
• CVE-2022-32158Splunk Enterprise deployment servers in versions before 8.1.…10
• CVE-2022-32159In openlibrary versions deploy-2016-07-0 through deploy-2021…