Detection: Persistent XSS in RapidDiag through User Interface Views

Updated Date: 2024-10-16 ID: ce6e1268-e01c-4df2-a617-0f034ed49a43 Author: Rod Soto, Splunk Type: TTP Product: Splunk Enterprise Security

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.

Search

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

Data Source

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

Macros Used

Name	Value
audit_searches	`index=_audit sourcetype=audittrail action=search`
persistent_xss_in_rapiddiag_through_user_interface_views_filter	`search *`

persistent_xss_in_rapiddiag_through_user_interface_views_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
T1189	Drive-by Compromise	Initial Access

KillChainPhase.DELIVERY

NistCategory.DE_CM

Cis18Value.CIS_10

APT19

APT28

APT32

APT37

APT38

Andariel

Axiom

BRONZE BUTLER

CURIUM

Daggerfly

Dark Caracal

Darkhotel

Dragonfly

Earth Lusca

Elderwood

Lazarus Group

Leafminer

Leviathan

Machete

Magic Hound

Mustard Tempest

PLATINUM

PROMETHIUM

Patchwork

RTM

Threat Group-3390

Transparent Tribe

Turla

Windigo

Windshift

Winter Vivern

Default Configuration

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

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Notable	Yes
Rule Title	`%name%`
Rule Description	`%description%`
Notable Event Fields	user, dest
Creates Risk Event	True

This configuration file applies to all detections of type TTP. These detections will use Risk Based Alerting and generate Notable Events.

Implementation

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

Splunk Vulnerabilities

Risk Based Analytics (RBA)

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

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

References

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

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	✅ Passing	N/A	N/A	N/A
Unit	✅ Passing	Dataset	`audittrail`	`audittrail`
Integration	✅ Passing	Dataset	`audittrail`	`audittrail`

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