Improper Handling and Insufficient Isolation of Specific Temporary Files in Splunk Enterprise
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
Splunk Enterprise · Splunk Cloud Platform
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
≥ 10.1.2507 · < 10.1.2507.19≥ 10.0.2503 · < 10.0.2503.13≥ 9.3.2411 · < 9.3.2411.127| No fix yet |
In Splunk Enterprise versions below 10.2.1, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below 10.4.2603.0, 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, and 9.3.2411.127, a low-privileged user that does not hold the `admin` or `power` Splunk roles could potentially perform a Remote Code Execution (RCE) by uploading a malicious file to the `$SPLUNK_HOME/var/run/splunk/apptemp` directory due to improper handling and insufficient isolation of temporary files within the `apptemp` directory.
From the CVE record · cisco
Splunk Enterprise and Splunk Cloud Platform improperly handle and isolate temporary files in the apptemp directory. An authenticated, low-privileged user without the `admin` or `power` role could potentially execute code remotely by uploading a malicious file to that directory. No user interaction is described.
Operators of Splunk Enterprise below 10.2.1, 10.0.5, 9.4.10, or 9.3.11, or Splunk Cloud Platform below 10.4.2603.0, 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, or 9.3.2411.127 should check their deployments.