Splunk Retired CVE-2022-32151 Detections After Patching TLS and Protocol Impersonation Risks
Patch & Detection Intelligence · 3 sources · Updated 3mo ago · First seen May 14, 2026

Splunk removed two security analytics tied to CVE-2022-32151 after stating the underlying issues were patched in current releases. The retired detections had been designed to flag Splunk forwarder connections where ssl=false and to identify weak TLS certificate-validation settings in Python httplib and urllib components across search heads and peers. Splunk warned that these conditions could expose sensitive data, allow interception or manipulation of traffic, and in some cases enable attackers to download or publish forwarder bundles, creating a path to arbitrary code execution.
The risks align with the broader ATT&CK technique T1001.003: Protocol or Service Impersonation, which covers malware and intrusion sets that disguise command-and-control traffic as legitimate services or protocols such as TLS and HTTP. MITRE documents how adversaries use fake TLS handshakes, spoofed record headers, and benign-looking HTTP headers, cookies, URI parameters, and POST bodies to evade inspection. In Splunk environments, weak or absent encryption can make that kind of impersonation harder to distinguish from normal traffic, which is why the detections had focused on missing encryption and certificate-validation weaknesses before being deprecated in version 5.6.0.


