Improper Access Control in System Source Types Configuration in Splunk Enterprise
Splunk Enterprise · Splunk Enterprise Cloud
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Enterprise Cloud |
|
Splunk Enterprise · Splunk Enterprise Cloud
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Enterprise Cloud |
|
| No fix yet |
In Splunk Enterprise versions below 9.4.2, 9.3.5, 9.2.7, and 9.1.10 and Splunk Cloud Platform versions below 9.3.2411.104, 9.3.2408.113, and 9.2.2406.119, a low-privileged user that does not hold the "admin" or "power" Splunk roles could create or overwrite [system source type](https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/9.2/configure-source-types/create-source-types) configurations by sending a specially-crafted payload to the `/servicesNS/nobody/search/admin/sourcetypes/` REST endpoint on the Splunk management port.
From the CVE record · cisco
Affected Splunk Enterprise and Splunk Cloud Platform versions allow a low-privileged user without the admin or power role to create or overwrite system source type configurations. The user can do this by sending a specially crafted payload to a REST endpoint on the Splunk management port; no other user interaction is described.
Operators running Splunk Enterprise below 9.4.2, 9.3.5, 9.2.7, or 9.1.10, or Splunk Cloud Platform below 9.3.2411.104, 9.3.2408.113, or 9.2.2406.119, should check their deployments.