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 ho…

Overview

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.

Affected

• splunk >= 9.3.0, < 9.3.12
• splunk >= 9.4.0, < 9.4.11
• splunk >= 10.0.0, < 10.0.5
• splunk >= 10.2.0, < 10.2.2
• splunk_cloud_platform >= 9.3.2411, < 9.3.2411.129
• splunk_cloud_platform >= 10.0.2503, < 10.0.2503.13
• splunk_cloud_platform >= 10.1.2507, < 10.1.2507.21
• splunk_cloud_platform >= 10.2.2510, < 10.2.2510.11
• splunk_cloud_platform >= 10.3.2512, < 10.3.2512.9
• splunk_cloud_platform = 10.4.2603

Remediation

Upgrade past the affected range:

• splunk 10.2.2
• splunk_cloud_platform 10.3.2512.9