Information Exposure 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.9, 3.9.23, and 3.8.70, a user who does not hold the "admin" or "power" Splunk roles could read sensitive Security Assertion Markup Language setup and instance settings information through Splunk Secure Gateway Representational State Transfer (REST) API endpoints. The vulnerability is possible because the affected Security Assertion Markup Language setup and instance settings REST API endpoints do not enforce authorization requirements before returning configuration information.
From the CVE record · cisco
Affected Splunk Secure Gateway REST API endpoints return sensitive SAML setup and instance settings information without enforcing authorization requirements. A user without the admin or power Splunk roles could read this information through those endpoints.
Teams running Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, or 9.4.14, or Splunk Secure Gateway versions below 3.10.9, 3.9.23, or 3.8.70, should check their deployments.