SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Deployment Server 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 10.1.2507.24, Cloud Platform 10.2.2510.18, Cloud Platform 10.3.2512.16 and 6 more.
In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, and 10.1.2507.24, an attacker could trick a user that holds a role with the `list_deployment_server` capability into running arbitrary Search Processing Language (SPL) searches on their behalf as `splunk-system-user`, allowing for access to stored credentials and indexed data.<br><br>The vulnerability is possible because Deployment Server endpoints in Splunk Web do not validate Cross-Site Request Forgery (CSRF) tokens on GET requests, and caller-supplied input is not correctly neutralized before it is placed into an SPL search.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Splunk | Cloud Platform | >=10.1.2507 <10.1.2507.24, >=10.2.2510 <10.2.2510.18, >=10.3.2512 <10.3.2512.16, >=10.4.2604 <10.4.2604.7, >=10.5.2605 <10.5.2605.0 | 10.1.2507.24, 10.2.2510.18, 10.3.2512.16, 10.4.2604.7, 10.5.2605.0 |
| Splunk | Enterprise | >=10.0 <10.0.8, >=10.2 <10.2.5, >=10.4 <10.4.1, >=9.4 <9.4.13 | 10.0.8, 10.2.5, 10.4.1, 9.4.13 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Enterprise, strongest first
Embed
A live severity badge for an advisory, README or ticket