Denial of Service through coldToFrozen.sh Script 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.21≥ 10.0.2503 · < 10.0.2503.13≥ 9.3.2411 · < 9.3.2411.129| No fix yet |
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.
From the CVE record · cisco
The coldToFrozen.sh script in the splunk_archiver app accepts arbitrary file paths and can rename critical Splunk directories. An authenticated, low-privileged user without the admin or power role could make the instance non-functional; no user interaction is described.
Operators of Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.11, or 9.3.12, or 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, or 9.3.2411.129 should check their deployments.