Authorization Bypass through Mission Control in Splunk Enterprise Security
Summary
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could overwrite Mission Control preference records for other users and remove saved filters and analyst queue settings from those records.
The vulnerability is possible because the...
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| SplunkSplunk Enterprise Security |
< 8.7.0→ 8.7.0 |
8.7.0 |
Original description The description as published by the source.
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could overwrite Mission Control preference records for other users and remove saved filters and analyst queue settings from those records.
The vulnerability is possible because the Mission Control user preferences Representational State Transfer (REST) API does not bind an update to the preference record that passes the authorization check.
The attack requires the user to obtain a preference record identifier that the product does not normally expose to that user. The user should not be able to exploit the vulnerability at will.
For more information see Overview of Mission Control in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/mission-control/overview-of-mission-control-in-splunk-enterprise-security) in the Splunk documentation.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- web psirt@cisco.com