Splunk RCE via Splunk Secure Gateway Splunk Mobile alerts feature

Description

The following analytic identifies potential exploitation attempts against the Splunk Secure Gateway App's Mobile Alerts feature in Splunk versions 9.0, 8.2.x, and 8.1.x. It detects suspicious activity by monitoring requests to the mobile alerts endpoint using specific URI paths and query parameters. This activity is significant because an authenticated user could exploit this vulnerability to execute arbitrary operating system commands remotely. If confirmed malicious, this could lead to unauthorized code execution, compromising the integrity and security of the Splunk environment.

Type: Hunting
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
Last Updated: 2024-05-16
Author: Rod Soto
ID: baa41f09-df48-4375-8991-520beea161be

Annotations

ATT&CK

ID	Technique	Tactic
T1210	Exploitation of Remote Services	Lateral Movement

Kill Chain Phase

Exploitation

NIST

DE.AE

CIS20

CIS 10

CVE

Search

`splunkda` uri_path="/servicesNS/nobody/splunk_secure_gateway/storage/collections/data/mobile_alerts*" sort="notification.created_at:-1" 
| table  clientip file host method uri_query sort 
| `splunk_rce_via_splunk_secure_gateway__splunk_mobile_alerts_feature_filter`

Macros

The SPL above uses the following Macros:

splunkda

splunk_rce_via_splunk_secure_gateway__splunk_mobile_alerts_feature_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.

uri_path
clientip
file
host
method
sort

How To Implement

This search only applies if Splunk Mobile Gateway is deployed in the vulnerable Splunk versions.

Known False Positives

This detection does not require you to ingest any new data. The detection does require the ability to search the _internal index. Focus of this search is "uri_path=/servicesNS/nobody/splunk_secure_gateway/storage/collections/data/mobile_alerts*" which is the injection point.

Associated Analytic Story

Splunk Vulnerabilities

RBA

Risk Score	Impact	Confidence	Message
81.0	90	90	Possible exploitation attempt from $clientip$

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

https://www.splunk.com/en_us/product-security.html

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

Twitter Facebook LinkedIn