Improper Access Control through REST API Endpoints in Splunk Secure Gateway
Splunk Enterprise · Splunk Secure Gateway
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Secure Gateway |
|
Splunk Enterprise · Splunk Secure Gateway
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Secure Gateway |
|
| No fix yet |
In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, and Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72, a user who does not hold the "admin" or "power" Splunk roles could access privileged Splunk Secure Gateway functionality. With this access, the user could cause Splunk Secure Gateway to sign attacker-controlled payloads. The vulnerability is possible because multiple Splunk Secure Gateway Representational State Transfer (REST) API endpoints do not enforce authorization requirements before processing requests.
From the CVE record · cisco
Multiple Splunk Secure Gateway REST API endpoints do not enforce authorization before processing requests. A user without the "admin" or "power" Splunk role could access privileged functionality and cause Splunk Secure Gateway to sign attacker-controlled payloads.
Operators of Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72, should check their deployments.