Insecure Default Access Control List through the REST API 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 Spacebridge asymmetric private keys, which are secrets that compromise affected Spacebridge private-key material stored in the app collection, through the Splunk Secure Gateway App Key Value Store Representational State Transfer (REST) API. The vulnerability is possible on instances upgraded from older Splunk Secure Gateway deployments when the private-key migration remains incomplete, leaving key material in a collection with an insecure default access control list.
From the CVE record · cisco
On affected Splunk Enterprise and Splunk Secure Gateway instances, a user without the admin or power role can read Spacebridge asymmetric private keys through the Secure Gateway App Key Value Store REST API. This requires an instance upgraded from an older Secure Gateway deployment where private-key migration remains incomplete, leaving the keys in a collection with an insecure default access control list.
Check Splunk Enterprise instances running versions below 10.4.2, 10.2.6, 10.0.9, or 9.4.14, and Splunk Secure Gateway instances running versions below 3.10.9, 3.9.23, or 3.8.70.