Description
Dashboards in Splunk Enterprise versions before 9.0 might let an attacker inject risky search commands into a form token when the token is used in a query in a cross-origin request. The result bypasses SPL safeguards for risky commands. See New capabilities can limit access to some custom and potentially risky commands (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/SPLsafeguards#New_capabilities_can_limit_access_to_some_custom_and_potentially_risky_commands) for more information. Note that the attack is browser-based and an attacker cannot exploit it at will.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Splunk, Inc Splunk Enterprise
9.0 to < 9.0affected
Splunk, Inc Splunk Cloud Platform
8.2 to < 8.2.2106affected
References
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates ↗
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0604.html ↗
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/SPLsafeguards#New_capabilities_can_limit_access_to_some_custom_and_potentially_risky_commands ↗
- https://research.splunk.com/application/splunk_command_and_scripting_interpreter_risky_commands/ ↗
- https://research.splunk.com/application/splunk_command_and_scripting_interpreter_risky_spl_mltk/ ↗
- https://research.splunk.com/application/splunk_command_and_scripting_interpreter_delete_usage/ ↗