Server-Side Request Forgery (SSRF) through Dashboard Studio PDF Export in Splunk Enterprise
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
Splunk Enterprise · Splunk Cloud Platform
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
≥ 10.1.2507 · < 10.1.2507.22≥ 9.3.2411 · < 9.3.2411.132| No fix yet |
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.
From the CVE record · cisco
Dashboard Studio PDF export in affected Splunk Enterprise and Splunk Cloud Platform versions can send server-side requests to arbitrary internal destinations. A low-privileged user without the admin or power role can exploit trusted-domain prefix matching and redirects that are not re-validated.
Teams running Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, or 9.3.13, or Splunk Cloud Platform versions below 10.4.2604.3, 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, or 9.3.2411.132 should check their deployments.