In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109 and 9.1.2308.207, an authenticated user could create an external lookup that calls a legacy internal function. The authenticated user could use this internal function to insert code into the Splunk platform installation directory. From there, the user could execute arbitrary code on the Splunk platform Instance.
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.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Splunk | Splunk | 9.0.0 (including) | 9.0.10 (excluding) |
Splunk | Splunk | 9.1.0 (including) | 9.1.5 (excluding) |
Splunk | Splunk | 9.2.0 (including) | 9.2.2 (excluding) |
Splunk_cloud_platform | Splunk | 9.1.2308 (including) | 9.1.2308.207 (excluding) |
Splunk_cloud_platform | Splunk | 9.1.2312 (including) | 9.1.2312.109 (excluding) |
Command injection vulnerabilities typically occur when:
Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks. Command injection is a common problem with wrapper programs.