Improper Authorization through the REST API in Splunk Enterprise
Summary
In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search with elevated privileges. The vulnerability lets the user acces...
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| SplunkSplunk Enterprise |
≥ 10.4, < 10.4.5→ 10.4.5 ≥ 10.2, < 10.2.9→ 10.2.9 ≥ 10.0, < 10.0.12→ 10.0.12 ≥ 9.4, < 9.4.17→ 9.4.17 |
10.4.5 10.2.9 10.0.12 9.4.17 |
Original description The description as published by the source.
In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search with elevated privileges. The vulnerability lets the user access or modify data and disrupt the Splunk Enterprise instance.
The vulnerability occurs because Splunk Enterprise does not enforce the required role-based authorization when it processes metric alert configuration through the REST API. Splunk Enterprise schedules the resulting search with elevated authorization and runs attacker-controlled search processing with that authorization.
For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- web psirt@cisco.com