Improper Input Validation through Protocol-Relative URL in Classic Dashboards 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 |
|
≥ 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.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could cause data exfiltration through classic dashboards by redirecting a victim to an external site using a protocol-relative URL in a drill-down link.<br><br>The vulnerability exists because the URL classifier in classic dashboards only recognizes `http://` and `https://` schemes when checking for external URLs. Protocol-relative URLs such as `//attacker.com` bypass this check entirely, and Splunk Web does not show the external-navigation warning dialog to the victim.
From the CVE record · cisco
Classic dashboards in affected Splunk versions fail to recognize protocol-relative drill-down URLs as external links. An authenticated user without the admin or power role can use such a link to redirect a victim to an external site without Splunk Web showing its external-navigation warning, potentially exfiltrating data when the victim follows the link.
Teams running Splunk Enterprise below 10.2.4, 10.0.7, 9.4.12, or 9.3.13, or Splunk Cloud Platform below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, or 9.3.2411.132 should check their deployments.