Denial of Service through coldToFrozen.sh Script 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.2, 10.0.5, 9.4.11, 9.3.12, 10.4.2603.1, and 5 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: partial
Summary
In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.11, and 9.3.12, and Splunk Cloud Platform versions below 10.4.2603.1, 10.3.2512.9, 10.2.2510.11, 10.1.2507.21, 10.0.2503.13, and 9.3.2411.129, a low-privileged user that does not hold the ‘admin’ or ‘power’ Splunk roles could cause a Denial of Service by exploiting the `coldToFrozen.sh` script in the `splunk_archiver` app to rename critical Splunk directories, making the instance non-functional.<br><br>The Denial of Service is possible because of missing input validation in the `coldToFrozen.sh` script, which accepts arbitrary file paths and renames them without restricting operations to safe directories.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Splunk Splunk Enterprise
From 10.2 · fixed in 10.2.2; From 10.0 · fixed in 10.0.5; From 9.4 · fixed in 9.4.11; From 9.3 · fixed in 9.3.12
- Splunk Splunk Cloud Platform
From 10.4.2603 · fixed in 10.4.2603.1; From 10.3.2512 · fixed in 10.3.2512.9; From 10.2.2510 · fixed in 10.2.2510.11; From 10.1.2507 · fixed in 10.1.2507.21; From 10.0.2503 · fixed in 10.0.2503.13; From 9.3.2411 · fixed in 9.3.2411.129