Improper Access Control Lets Low-Privilege Users Suppress Read-Only Alerts 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 |
|
| No fix yet |
In Splunk Enterprise versions below 9.4.2, 9.3.5, 9.2.6, and 9.1.9 and Splunk Cloud Platform versions below 9.3.2411.103, 9.3.2408.112, and 9.2.2406.119, a low-privileged user that does not hold the "admin" or "power" Splunk roles, and has read-only access to a specific alert, could suppress that alert when it triggers. See [Define alert suppression groups to throttle sets of similar alerts](https://help.splunk.com/en/splunk-enterprise/alert-and-respond/alerting-manual/9.4/manage-alert-trigger-conditions-and-throttling/define-alert-suppression-groups-to-throttle-sets-of-similar-alerts).
From the CVE record · cisco
Affected Splunk Enterprise and Splunk Cloud Platform versions allow a low-privileged user to suppress a specific alert when it triggers. The user must have read-only access to that alert and lack both the "admin" and "power" Splunk roles.
Teams running Splunk Enterprise below 9.4.2, 9.3.5, 9.2.6, or 9.1.9, or Splunk Cloud Platform below 9.3.2411.103, 9.3.2408.112, or 9.2.2406.119, should check their deployments.