GitHub Repo

Detection: Splunk DOS Via Dump SPL Command

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: Detection is deprecated as the associated CVEs have been patched in the latest Splunk release.

Removed in version: 5.6.0

If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2026-05-14 ID: fb0e6823-365f-48ed-b09e-272ac4c1dad6 Author: Rod Soto Type: Hunting Product: Splunk Enterprise Security

Description

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.

1`splunk_crash_log` "*Segmentation fault*" 
2| stats count by host _time 
3| `splunk_dos_via_dump_spl_command_filter`

Data Source

Name Platform Sourcetype Source
Splunk Splunk icon Splunk 'splunkd_ui_access' 'splunkd_ui_access.log'

Macros Used

Name Value
splunk_crash_log (index=_internal AND sourcetype=splunkd_crash_log)
splunk_dos_via_dump_spl_command_filter ``
splunk_dos_via_dump_spl_command_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK
+ Kill Chain Phases
+ NIST
+ CIS
- Threat Actors
ID Technique Tactic
T1499.004

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting Value
Disabled true
Cron Schedule N/A
Earliest Time N/A
Latest Time N/A
Schedule Window N/A
Creates Finding (Notable) No
Creates Intermediate Finding (Risk Event) No
Hunting detections do not generate a Finding (Notable) or Intermediate Findings (Risk Events).

Implementation

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

References

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation Not Applicable N/A N/A N/A
Unit Not Applicable N/A N/A N/A

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

Source: GitHub |

Version: 6