Risky Command Safeguards Bypass in “/app/search/search“ endpoint through “s“ parameter in 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 Cloud Platform 9.1.2308.212, Cloud Platform 9.1.2312.208, Cloud Platform 9.2.2403.113 and 5 more.
In Splunk Enterprise versions below 9.3.3, 9.2.5, and 9.1.8 and Splunk Cloud Platform versions below 9.3.2408.103, 9.2.2406.108, 9.2.2403.113, 9.1.2312.208 and 9.1.2308.212, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands on the “/app/search/search“ endpoint through its “s“ parameter. <br>The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Splunk | Cloud Platform | >=9.1.2308 <9.1.2308.212, >=9.1.2312 <9.1.2312.208, >=9.2.2403 <9.2.2403.113, >=9.2.2406 <9.2.2406.108, >=9.3.2408 <9.3.2408.103 | 9.1.2308.212, 9.1.2312.208, 9.2.2403.113, 9.2.2406.108, 9.3.2408.103 |
| Splunk | Enterprise | >=9.1 <9.1.8, >=9.2 <9.2.5, >=9.3 <9.3.3 | 9.1.8, 9.2.5, 9.3.3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Enterprise, strongest first
Embed
A live severity badge for an advisory, README or ticket