Missing Authorization 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.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.10, 3.9.24, and 3.8.71, a user who holds a Splunk role with permissions to list storage passwords but does not hold Splunk Secure Gateway administration privileges could access Mobile Device Management signing secrets that compromise all affected mobile-device enrollment trust through Splunk Secure Gateway. The vulnerability is possible because Splunk Secure Gateway Representational State Transfer (REST) API endpoints for deployment bundle, Security Assertion Markup Language setup, and companion app workflows do not require Splunk Secure Gateway administration privileges before processing requests.
From the CVE record · cisco
Splunk Secure Gateway REST API endpoints for deployment bundles, SAML setup, and companion app workflows do not require Secure Gateway administration privileges before processing requests. A user with a Splunk role that can list storage passwords, but lacks Secure Gateway administration privileges, could access Mobile Device Management signing secrets and compromise affected mobile-device enrollment trust.
Teams running Splunk Enterprise below 10.4.2, 10.2.6, 10.0.9, or 9.4.14, or Splunk Secure Gateway below 3.10.10, 3.9.24, or 3.8.71, should check their deployments.