In Splunk Enterprise versions below 9.4.1, 9.3.3, 9.2.5, and 9.1.8, and versions below 3.8.38 and 3.7.23 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a search using the permissions of a higher-privileged user that could lead to disclosure of sensitive information.The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated low-privileged user should not be able to exploit the vulnerability at will.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Splunk | Splunk | 9.1.0 (including) | 9.1.8 (excluding) |
| Splunk | Splunk | 9.2.0 (including) | 9.2.5 (excluding) |
| Splunk | Splunk | 9.3.0 (including) | 9.3.3 (excluding) |
| Splunk | Splunk | 9.4.0 (including) | 9.4.0 (including) |
| Splunk_secure_gateway | Splunk | 3.7.0 (including) | 3.7.23 (excluding) |
| Splunk_secure_gateway | Splunk | 3.8.0 (including) | 3.8.38 (excluding) |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: