Try in Splunk Security Cloud

Description

In Splunk Enterprise versions below 9.0.5, 8.2.11, and 8.1.14, an attacker can exploit a vulnerability in the dump SPL command to cause a Denial of Service by crashing the Splunk daemon.

  • Type: Hunting
  • Product: Splunk Enterprise

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

Annotations

ATT&CK

ATT&CK

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

Macros

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

RBA

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.

Reference

Test Dataset

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 | version: 1