Splunk RBAC Bypass On Indexing Preview REST Endpoint
Description
An unauthorized user can use the /services/indexing/preview REST endpoint to overwrite search results if they know the search ID (SID) of an existing search job.
- Type: Hunting
-
Product: Splunk Enterprise
- Last Updated: 2023-05-10
- Author: Rod Soto
- ID: bbe26f95-1655-471d-8abd-3d32fafa86f8
Annotations
ATT&CK
Kill Chain Phase
- Exploitation
NIST
- DE.AE
CIS20
- CIS 10
CVE
Search
1
2
3
`splunkda` method="POST" uri="*/services/indexing/preview*"
| table host clientip status useragent user uri_path
| `splunk_rbac_bypass_on_indexing_preview_rest_endpoint_filter`
Macros
The SPL above uses the following Macros:
splunk_rbac_bypass_on_indexing_preview_rest_endpoint_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
- clientip
- status
- useragent
- user
- uri_path
How To Implement
This search does not require additional data ingestion. It requires the ability to search _internal index.
Known False Positives
This is a hunting search which provides verbose results against this endpoint. Operator must consider things such as IP address, useragent and user(specially low privelege) and host to investigate possible attack.
Associated Analytic Story
RBA
Risk Score | Impact | Confidence | Message |
---|---|---|---|
15.0 | 30 | 50 | Review $clientip$ access to indexing preview endpoint from low privilege user |
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