Improper Handling and Insufficient Isolation of Specific Temporary Files in Splunk Enterprise
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.2.1, 10.0.5, 9.4.10, 9.3.11, 10.3.2512.5, and 4 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- Splunk Splunk Enterprise
From 10.2 · fixed in 10.2.1; From 10.0 · fixed in 10.0.5; From 9.4 · fixed in 9.4.10; From 9.3 · fixed in 9.3.11
- Splunk Splunk Cloud Platform
From 10.3.2512 · fixed in 10.3.2512.5; From 10.2.2510 · fixed in 10.2.2510.9; From 10.1.2507 · fixed in 10.1.2507.19; From 10.0.2503 · fixed in 10.0.2503.13; From 9.3.2411 · fixed in 9.3.2411.127