Command Injection using External Lookups
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
| No fix yet |
Splunk Enterprise · Splunk Cloud Platform
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
| No fix yet |
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.
From the CVE record · Splunk
Affected Splunk Enterprise and Splunk Cloud Platform versions let an authenticated user create an external lookup that calls a legacy internal function. The user could use it to insert code into the installation directory and execute arbitrary code on the Splunk platform instance.
Operators running Splunk Enterprise below 9.2.2, 9.1.5, or 9.0.10, or Splunk Cloud Platform below 9.1.2312.109 or 9.1.2308.207, should check their installations.