Try in Splunk Security Cloud


The following analytic identifies a potential Denial of Service (DoS) attack exploiting the dump SPL command in vulnerable Splunk Enterprise versions. It detects this activity by searching the splunk_crash_log for segmentation fault entries, indicating a crash of the Splunk daemon. This activity is significant for a SOC because it can disrupt the availability of Splunk services, impacting monitoring and incident response capabilities. If confirmed malicious, this attack could render Splunk Enterprise unusable, severely hindering an organization's ability to detect and respond to other security threats.

  • Type: Hunting
  • Product: Splunk Enterprise

  • Last Updated: 2024-05-03
  • Author: Rod Soto
  • ID: fb0e6823-365f-48ed-b09e-272ac4c1dad6




ID Technique Tactic
T1499.004 Application or System Exploitation Impact
Kill Chain Phase
  • Actions On Objectives
  • DE.AE
  • CIS 10
`splunk_crash_log` "*Segmentation fault*" 
| stats count by host _time 
| `splunk_dos_via_dump_spl_command_filter`


The SPL above uses the following Macros:

:information_source: splunk_dos_via_dump_spl_command_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.

  • host
  • source
  • event_message
  • status
  • _time

How To Implement

This search does not require additional ingestion of data. Requires the ability to search _internal index and monitor segmentation faults.

Known False Positives

Segmentation faults may occur due to other causes, so this search may produce false positives

Associated Analytic Story


Risk Score Impact Confidence Message
100.0 100 100 Possible denial of service attack with Victim $host$

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