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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
| Link | Tags |
|---|---|
| https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates | release notes vendor advisory |
| https://www.splunk.com/en_us/product-security/announcements/svd-2022-0604.html | vendor advisory |
| https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/SPLsafeguards#New_capabilities_can_limit_access_to_some_custom_and_potentially_risky_commands | mitigation vendor advisory |
| https://research.splunk.com/application/splunk_command_and_scripting_interpreter_risky_commands/ | mitigation vendor advisory |
| https://research.splunk.com/application/splunk_command_and_scripting_interpreter_risky_spl_mltk/ | mitigation vendor advisory |
| https://research.splunk.com/application/splunk_command_and_scripting_interpreter_delete_usage/ | mitigation vendor advisory |