In Splunk Enterprise versions below 9.2.3 and 9.1.6, and Splunk Secure Gateway versions on Splunk Cloud Platform versions below 3.4.259, 3.6.17, and 3.7.0, a low-privileged user that does not hold the admin or power Splunk roles can see App Key Value Store (KV Store) deployment configuration and public/private keys in the Splunk Secure Gateway App.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Splunk | Splunk | 9.1.0 (including) | 9.1.6 (excluding) |
| Splunk | Splunk | 9.2.0 (including) | 9.2.3 (excluding) |
| Splunk_cloud_platform | Splunk | * | 3.4.259 (excluding) |
| Splunk_cloud_platform | Splunk | 3.6.0 (including) | 3.6.17 (excluding) |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: