Improper Access Control in Background Job Submission in Splunk Enterprise
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
Splunk Enterprise · Splunk Cloud Platform
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
| No fix yet |
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.
From the CVE record · cisco
Affected Splunk Enterprise and Splunk Cloud Platform versions may expose sensitive search results to a low-privileged user without the admin or power role. If Splunk Enterprise runs an administrative search job in the background and the user guesses its unique Search ID (SID), the user could retrieve that job’s results.
Teams running Splunk Enterprise versions below 9.4.4, 9.3.6, or 9.2.8, or Splunk Cloud Platform versions below 9.3.2411.111, 9.3.2408.119, or 9.2.2406.122, should check their deployments.