Server-Side Request Forgery (SSRF) through Dashboard Studio PDF Export in Splunk Enterprise
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.2.4, 10.0.7, 9.4.12, 9.3.13, 10.4.2604.3, and 4 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Splunk Splunk Enterprise
From 10.2 · fixed in 10.2.4; From 10.0 · fixed in 10.0.7; From 9.4 · fixed in 9.4.12; From 9.3 · fixed in 9.3.13
- Splunk Splunk Cloud Platform
From 10.4.2604 · fixed in 10.4.2604.3; From 10.3.2512 · fixed in 10.3.2512.12; From 10.2.2510 · fixed in 10.2.2510.14; From 10.1.2507 · fixed in 10.1.2507.22; From 9.3.2411 · fixed in 9.3.2411.132