Improper Access Control in Data Model Acceleration 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.19≥ 10.0.2503 · < 10.0.2503.13≥ 9.3.2411 · < 9.3.2411.127| No fix yet |
In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below 10.4.2603.0, 10.3.2512.6, 10.2.2510.10, 10.1.2507.19, 10.0.2503.13, and 9.3.2411.127, a low-privileged user that does not hold the `admin` or `power` Splunk roles, has write permission on the app, and does not hold the high-privilege capability `accelerate_datamodel`, could turn on or off Data Model Acceleration due to improper access control.
From the CVE record · cisco
Improper access control in Splunk Enterprise and Splunk Cloud Platform lets a low-privileged user turn Data Model Acceleration on or off. The user must have write permission on the app but need not have the `admin` or `power` role or the `accelerate_datamodel` capability.
Teams running Splunk Enterprise below 10.2.2, 10.0.5, 9.4.10, or 9.3.11, or Splunk Cloud Platform below 10.4.2603.0, 10.3.2512.6, 10.2.2510.10, 10.1.2507.19, 10.0.2503.13, or 9.3.2411.127 should check their deployments.