In Splunk Enterprise versions below 9.4.4, 9.3.6, and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.111, 9.3.2408.119, and 9.2.2406.122, a low-privileged user that does not hold the admin or power Splunk roles could access sensitive search results if Splunk Enterprise runs an administrative search job in the background. If the low privileged user guesses the search job’s unique Search ID (SID), the user could retrieve the results of that job, potentially exposing sensitive search results. For more information see https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.0/manage-jobs/about-jobs-and-job-management and https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.0/manage-jobs/manage-search-jobs.
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.2.0 (including) | 9.2.8 (excluding) |
| Splunk | Splunk | 9.3.0 (including) | 9.3.6 (excluding) |
| Splunk | Splunk | 9.4.0 (including) | 9.4.4 (excluding) |
| Splunk_cloud_platform | Splunk | 9.2.2406 (including) | 9.2.2406.122 (excluding) |
| Splunk_cloud_platform | Splunk | 9.3.2408 (including) | 9.3.2408.119 (excluding) |
| Splunk_cloud_platform | Splunk | 9.3.2411 (including) | 9.3.2411.111 (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: