Loading story…
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.
See real exploitation activity before you spend the cycle.
2 events from the most recent confirmed update back to the earliest known activity.
Splunk Threat Research removed the detections "Splunk Digital Certificates Lack of Encryption" and "Splunk Protocol Impersonation Weak Encryption Configuration" from its content library, stating the associated CVEs had been patched in the latest Splunk release. Both notices say the detections were removed in content library version 5.6.0 and are no longer maintained.
Splunk published product security advisories SVD-2022-0601 and SVD-2022-0607 covering vulnerabilities including CVE-2022-32151, which later became the basis for related detections in Splunk Threat Research content.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
3 references tracked. Mallory keeps watching after this page renders.
research.splunk.com
Open sourceresearch.splunk.com
Open sourceattack.mitre.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Splunk documented and later retired detections for protocol impersonation and weak-encryption scenarios tied to improper certificate handling in its platform and Python3 client libraries. The detections targeted use of insecure default self-signed certificates and SSL validation cases where certificate checks were enabled without hostname verification, conditions associated with **CVE-2022-32152** that could allow man-in-the-middle interception, data alteration, and unauthorized access. The retired analytics searched `splunkd` logs for X.509 certificate warnings and highlighted hosts, certificate common names, components, and log levels linked to unsafe TLS use. Splunk said the issue has been patched in current releases, recommended upgrading to **Splunk 9**, and advised replacing default self-signed certificates and enabling full TLS hostname validation; the risk aligns with the broader ATT&CK concept of adversaries abusing or obtaining digital certificates under **T1588.004** to support impersonation and trusted communications.
Aug 12, 2026
Splunk has removed several security analytics from its Threat Research content library after the underlying vulnerabilities were patched in current releases, including detections tied to path traversal, SPL injection, CSRF, unauthorized admin account creation, and Analytics Workspace data exfiltration. The retired content covered **CVE-2022-26889**, **CVE-2022-43566**, **CVE-2023-22942**, and **CVE-2023-22933**, with detections aimed at spotting exploitation attempts in on-premises deployments through internal access logs, audit searches, and REST API queries. The withdrawn detections had been designed to identify attacks such as crafted `../` traversal requests, abuse of the Splunk Secure Gateway `kvstore_client` endpoint, suspicious `sid` query activity in Analytics Workspace, and the presence of nonstandard administrative accounts that could indicate persistence or privilege escalation. Splunk said some analytics were deprecated because they were patched and no longer maintained, while at least one lookup file editing path traversal detection was removed because it did not accurately detect malicious activity and was ineffective against obfuscated requests; several notices also warned of false positives, disabled-by-default status, and limited usefulness without manual investigation.
Aug 12, 2026
Splunk has removed several Enterprise Security detections that were built to identify abuse of risky Search Processing Language (SPL) commands, including **"Splunk Command and Scripting Interpreter Risky SPL MLTK"**, **"Detect Risky SPL using Pretrained ML Model"**, and **"Splunk risky Command Abuse disclosed february 2023"**. The analytics monitored `Splunk_Audit.Search_Activity` data for ad hoc searches using commands such as `collect`, `delete`, `fit`, `outputcsv`, `outputlookup`, `run`, `script`, `sendalert`, `sendemail`, and `tscollect`, which could be abused to bypass warnings, escalate privileges, delete data, exfiltrate information, or support arbitrary code execution and persistence. Splunk said the detections were disabled by default and mapped to ATT&CK techniques including `T1059`, `T1202`, and `T1548`. The retired content relied on the **Machine Learning Toolkit (MLTK)** and, in some cases, pretrained models or per-user baselines to flag anomalous long-running risky searches or suspicious command text. Splunk originally promoted the approach as a way to complement rule-based detections for exploitation tied to **`CVE-2022-32154`** and later risky-command vulnerabilities, but the company has since withdrawn the analytics from its Threat Research library because the affected flaws have been patched in current Splunk releases. Splunk also noted operational drawbacks, including false positives from legitimate long-running searches and added compute requirements for model training in larger environments.
Aug 15, 2026