Try in Splunk Security Cloud


On May 3rd, 2022, Splunk published a security advisory for a Path traversal in search parameter that can potentiall allow SPL injection. An attacker can cause the application to load data from incorrect endpoints, urls leading to outcomes such as running arbitrary SPL queries.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2022-04-29
  • Author: Rod Soto, Splunk
  • ID: dfe55688-82ed-4d24-a21b-ed8f0e0fda99


ID Technique Tactic
T1083 File and Directory Discovery Discovery
Kill Chain Phase
  • Exploitation
  • CIS 3
  • CIS 5
  • CIS 16
ID Summary CVSS
CVE-2022-26889 The lack of sanitization in a relative url path in a search parameter allows for arbitrary injection of external content in Splunk Enterprise versions before 8.1.2. 7.5
| search "\/..\/..\/..\/..\/..\/..\/..\/..\/..\/"  
| stats count by status clientip method uri_path uri_query 
| `path_traversal_spl_injection_filter`


The SPL above uses the following Macros:

Note that path_traversal_spl_injection_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required field

  • status
  • clientip
  • method
  • uri_path
  • uri_query

How To Implement

This detection does not require you to ingest any new data. The detection does require the ability to search the _internal index. This search will provide search UI requests with path traversal parameter (“../../../../../../../../../”) which shows exploitation attempts.

Known False Positives

This search may find additional path traversal exploitation attempts.

Associated Analytic story


Risk Score Impact Confidence Message
40.0 50 80 Path traversal exploitation attempt from $clientip$


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1