Missing Authorization through Sourcetype Renaming in Splunk Web for Splunk Enterprise
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Enterprise 10.0.11, Enterprise 10.2.8, Enterprise 10.4.4 and 1 more.
In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could create, move, edit, or delete sourcetype renaming configurations that they own in apps that they do not have permission to access. The vulnerability is possible when Splunk Web is turned on because Splunk Web does not verify the required app permissions before it performs sourcetype renaming operations. For more information see Rename source types at search time (https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.6/configure-source-types/rename-source-types-at-search-time) in the Splunk documentation.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Splunk | Enterprise | >=10.0 <10.0.11, >=10.2 <10.2.8, >=10.4 <10.4.4, >=9.4 <9.4.16 | 10.0.11, 10.2.8, 10.4.4, 9.4.16 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Enterprise, strongest first
Embed
A live severity badge for an advisory, README or ticket