Headline
CVE-2023-22939: Splunk risky Command Abuse disclosed february 2023
In Splunk Enterprise versions below 8.1.13, 8.2.10, and 9.0.4, the ‘map’ search processing language (SPL) command lets a search bypass SPL safeguards for risky commands. The vulnerability requires a higher privileged user to initiate a request within their browser and only affects instances with Splunk Web enabled.
Try in Splunk Security Cloud
Description
In February 2023, Splunk disclosed several vulnerabilities affecting Splunk Enterprise commands deemed risky. The following hunting search includes the following commands and versions. Command ‘createrss’ (versions 8.1.13, 8.2.10), pivot (8.1.13,8.2.10,9.0.4), display.page.search.patterns.sensitivity(versions below 8.1.13,8.2.10,9.0.4), search_listener, map, collect (8.1.13,8.2.10,9.0.4). For more information please review Splunk Vulnerabilities Disclosure, February 2023. Link can be found in reference.
Type: Hunting
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
Last Updated: 2023-02-14
Author: Chase Franklin, Rod Soto, Eric McGinnis, Splunk
ID: ee69374a-d27e-4136-adac-956a96ff60fd
AnnotationsATT&CK
ATT&CK
ID
Technique
Tactic
T1548
Abuse Elevation Control Mechanism
Privilege Escalation, Defense Evasion
Kill Chain Phase
- Exploitation
NIST
- DE.CM
CIS20
- CIS 3
- CIS 5
- CIS 16
CVESearch
1
2
3
4
5
6
| tstats 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
| `drop_dm_object_name(Search_Activity)`
| lookup splunk_risky_command splunk_risky_command as search output splunk_risky_command description vulnerable_versions CVE other_metadata
| where splunk_risky_command != "false"
| `splunk_risky_command_abuse_disclosed_february_2023_filter`
Macros
The SPL above uses the following Macros:
splunk_risky_command_abuse_disclosed_february_2023_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Lookups
The SPL above uses the following Lookups:
- splunk_risky_command with data
Required fields
List of fields required to use this analytic.
- search
- info
- user
- search_type
- count
How To Implement
Requires implementation of Splunk_Audit.Search_Activity datamodel.
Known False Positives
This search encompasses many commands.
Associated Analytic Story
- Splunk Vulnerabilities
RBA
Risk Score
Impact
Confidence
Message
25.0
50
50
Use of risky splunk command $splunk_risky_command$ detected by $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
- 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
- https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1548/splunk/splunk_createrss_command_abuse.log
source | version: 1