Description
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.
Problem types
Product status
10.0 (custom) before 10.0.5
9.4 (custom) before 9.4.11
9.3 (custom) before 9.3.12
10.3.2512 (custom) before 10.3.2512.9
10.2.2510 (custom) before 10.2.2510.11
10.1.2507 (custom) before 10.1.2507.21
10.0.2503 (custom) before 10.0.2503.13
9.3.2411 (custom) before 9.3.2411.129
Credits
Alex Hordijk (hordalex)
References
advisory.splunk.com/advisories/SVD-2026-0504