| ID | Technique | Tactic |
|---|---|---|
| T1202 | Indirect Command Execution | Stealth |
| T1548 | Abuse Elevation Control Mechanism | Privilege Escalation |
Detection: Splunk risky Command Abuse disclosed february 2023
REMOVED DETECTION
This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.
Reason: Detection is deprecated as the associated CVEs have been patched in the latest Splunk release.
Removed in version: 5.6.0
If you have any questions or concerns, please reach out to us at research@splunk.com.
Description
The following analytic identifies the execution of high-risk commands associated with various Splunk vulnerability disclosures. It leverages the Splunk_Audit.Search_Activity datamodel to detect ad-hoc searches by non-system users that match known risky commands. This activity is significant for a SOC as it may indicate attempts to exploit known vulnerabilities within Splunk, potentially leading to unauthorized access or data exfiltration. If confirmed malicious, this could allow attackers to execute arbitrary code, escalate privileges, or persist within the environment, posing a severe threat to the organization's security posture.
Search
1
2| tstats fillnull_value="N/A" count min(_time) as firstTime max(_time) as lastTime from datamodel=Splunk_Audit.Search_Activity where Search_Activity.search_type=adhoc Search_Activity.user!=splunk-system-user by Search_Activity.search Search_Activity.info Search_Activity.total_run_time Search_Activity.user Search_Activity.search_type
3| `drop_dm_object_name(Search_Activity)`
4| lookup splunk_risky_command splunk_risky_command as search output splunk_risky_command description vulnerable_versions CVE
5| where splunk_risky_command != "false"
6| `security_content_ctime(firstTime)`
7| `security_content_ctime(lastTime)`
8| `splunk_risky_command_abuse_disclosed_february_2023_filter`
Data Source
| Name | Platform | Sourcetype | Source |
|---|---|---|---|
| Splunk | 'splunkd_ui_access' |
'splunkd_ui_access.log' |
Macros Used
| Name | Value |
|---|---|
| drop_dm_object_name | `` |
| splunk_risky_command_abuse_disclosed_february_2023_filter | `` |
splunk_risky_command_abuse_disclosed_february_2023_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
CVE
Default Configuration
This detection is configured by default in Splunk Enterprise Security to run with the following settings:
| Setting | Value |
|---|---|
| Disabled | true |
| Cron Schedule | N/A |
| Earliest Time | N/A |
| Latest Time | N/A |
| Schedule Window | N/A |
| Creates Finding (Notable) | No |
| Creates Intermediate Finding (Risk Event) | No |
Implementation
Requires implementation of Splunk_Audit.Search_Activity datamodel.
Known False Positives
This search encompasses many commands.
Associated Analytic Story
References
Detection Testing
| Test Type | Status | Dataset | Source | Sourcetype |
|---|---|---|---|---|
| Validation | Not Applicable | N/A | N/A | N/A |
| Unit | Not Applicable | N/A | N/A |
N/A |
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: 9