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. 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. See Set a retirement and archiving policy and role-based user access in the Splunk documentation for more information.
Upgrade Splunk Enterprise to versions 10.2.2, 10.0.5, 9.4.11, 9.3.12, or higher. Splunk is actively monitoring and patching Splunk Cloud Platform instances.
Turn off the Splunk Archiver app. See Manage app and add-on objects in the Splunk documentation. Note: If you use frozen bucket archiving with the splunk_archiver app, turning off the app will stop automated cold-to-frozen bucket transitions.
Splunk rates this vulnerability a 7.1, High, with a CVSSv3.1 vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. If you do not use the Splunk Archiver app, there should be no impact and the severity would be Informational.
Alex Hordijk (hordalex)
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
