Try in Splunk Security Cloud

Description

The following analytic identifies potential persistent Cross-Site Scripting (XSS) attacks in Splunk Enterprise 9.0 versions before 9.0.4 through user interface views. It leverages audit logs from the audit_searches data source to detect actions involving Base64-encoded images in error messages. This activity is significant because it can allow attackers to inject malicious scripts that execute in the context of other users, leading to unauthorized actions or data exposure. If confirmed malicious, this could result in persistent control over the affected Splunk instance, compromising its integrity and confidentiality.

  • Type: TTP

  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-05-24
  • Author: Rod Soto, Splunk
  • ID: ce6e1268-e01c-4df2-a617-0f034ed49a43

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1189 Drive-by Compromise Initial Access
Kill Chain Phase
  • Delivery
NIST
  • DE.CM
CIS20
  • CIS 10
CVE 


1
2
3
4



`audit_searches` path=/opt/splunk/etc/users/*/search/local/data/ui/views/* action=* 
|table user action roles info roles path 
| dedup user action 
| `persistent_xss_in_rapiddiag_through_user_interface_views_filter`

Macros

The SPL above uses the following Macros:

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

  • user
  • action
  • roles
  • info
  • roles
  • path

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

Known False Positives

This is a hunting search, it will not deobfuscate base64 payload, it provides however it will provide what user added the view artifact and what user opened it. It will require further investigation based on the information presented by this hunting search.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
25.0 50 50 A potential XSS attempt has been detected from $user$

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