Information Disclosure through External Content Restriction Bypass 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 malicious classic dashboard that exfiltrates sensitive data to an external server when a higher-privileged user views it, bypassing the external content restriction through a Cascading Style Sheets (CSS) injection.<br><br>The Trusted Domains security check does not fully validate inline style attribute values, which can allow for outbound requests to untrusted domains and credential exfiltration when a victim views a crafted dashboard.
From the CVE record · cisco
Splunk Enterprise and Splunk Cloud Platform do not fully validate inline style values in classic dashboards. An authenticated user without the admin or power role can craft a dashboard that sends sensitive data to an external server when a higher-privileged user views it.
Operators of Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, or 9.3.13, or Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, or 9.3.2411.132 should check their deployments.