Server-Side Request Forgery (SSRF) through Dashboard Studio PDF Export 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.22, Cloud Platform 10.2.2510.14, Cloud Platform 10.3.2512.12 and 6 more.
In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.4.2604.3, 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could send server-side requests to arbitrary internal destinations through the Dashboard Studio PDF export feature. The vulnerability exists because the trusted-domain validation uses a prefix match that can be bypassed with attacker-controlled subdomains (for example, docs.splunk.com.evil.com), and because the PDF export service follows HTTP redirects automatically without re-validating each redirect target against the allowlist.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Splunk | Cloud Platform | >=10.1.2507 <10.1.2507.22, >=10.2.2510 <10.2.2510.14, >=10.3.2512 <10.3.2512.12, >=10.4.2604 <10.4.2604.3, >=9.3.2411 <9.3.2411.132 | 10.1.2507.22, 10.2.2510.14, 10.3.2512.12, 10.4.2604.3, 9.3.2411.132 |
| Splunk | Enterprise | >=10.0 <10.0.7, >=10.2 <10.2.4, >=9.3 <9.3.13, >=9.4 <9.4.12 | 10.0.7, 10.2.4, 9.3.13, 9.4.12 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Enterprise, strongest first
Embed
A live severity badge for an advisory, README or ticket