Try in Splunk Security Cloud


The following analytic identifies attempts at path traversal in search parameters, which can lead to SPL injection. It detects this activity by searching for specific patterns in the _internal index that indicate path traversal attempts (e.g., "../../../../"). This activity is significant for a SOC because it can allow an attacker to manipulate the application to load data from incorrect endpoints, potentially running arbitrary SPL queries. If confirmed malicious, this could lead to unauthorized data access, code execution, or further exploitation of the Splunk environment.

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

  • Last Updated: 2024-05-26
  • Author: Rod Soto, Splunk
  • ID: dfe55688-82ed-4d24-a21b-ed8f0e0fda99




ID Technique Tactic
T1083 File and Directory Discovery Discovery
Kill Chain Phase
  • Exploitation
  • DE.CM
  • CIS 10
| search "\/..\/..\/..\/..\/..\/..\/..\/..\/..\/"  
| stats count by host status clientip method uri_path uri_query 
| `path_traversal_spl_injection_filter`


The SPL above uses the following Macros:

:information_source: 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 fields

List of fields required to use this analytic.

  • 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. This detection is meant for on premise environments, and if executed on internet facing servers without a WAF may produce a lot of results. This detection will not work against obfuscated path traversal requests.

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$

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


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: 3