Improper Input Validation through Classic Dashboard CSS 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 craft a classic dashboard that exfiltrates sensitive data from the browser of a higher-privileged user who views it.
The exfiltration is possible because classic dashboard panels do not fully validate style attribute values, which can allow for requests to reach external domains outside the configured Trusted Domains List.
The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will.
From the CVE record · cisco
Classic dashboard panels do not fully validate style attribute values, allowing requests to external domains outside the configured Trusted Domains List. A low-privileged user without the admin or power role could craft a dashboard that exfiltrates sensitive data from a higher-privileged user's browser, but must trick that user into initiating a request.
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.