Low-privileged user could run search as nobody in SplunkDeploymentServerConfig app
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
| No fix yet |
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.3.1, and 9.2.0 versions below 9.2.3, and Splunk Cloud Platform versions below 9.2.2403.103, 9.1.2312.200, 9.1.2312.110 and 9.1.2308.208, a low-privileged user that does not hold the "admin" or "power" Splunk roles could run a search as the "nobody" Splunk user in the SplunkDeploymentServerConfig app. This could let the low-privileged user access potentially restricted data.
From the CVE record · Splunk
Affected Splunk Enterprise and Splunk Cloud Platform versions allow an authenticated, low-privileged user without the admin or power role to run a search as the nobody Splunk user in the SplunkDeploymentServerConfig app. This could expose potentially restricted data.
Operators of Splunk Enterprise versions below 9.3.1 or 9.2.0 versions below 9.2.3, and Splunk Cloud Platform versions below 9.2.2403.103, 9.1.2312.200, 9.1.2312.110, or 9.1.2308.208, should check their deployments.