SPL Injection through the REST API in Splunk Secure Gateway
What fixes it
- 10.4.4Splunk EnterpriseCVE List
- 10.2.8Splunk EnterpriseCVE List
- 10.0.11Splunk EnterpriseCVE List
- 9.4.16Splunk EnterpriseCVE List
- 3.10.12Splunk Secure GatewayCVE List
- 3.9.26Splunk Secure GatewayCVE List
Show all 7 fixed versions
- 3.8.73Splunk Secure GatewayCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and Splunk Secure Gateway versions below 3.10.12, 3.9.26, and 3.8.73, a user who does not hold the "admin" or "power" Splunk roles could view dashboard and report listings beyond the requested filter scope while remaining within objects that the user can access. The vulnerability is possible because Splunk Secure Gateway does not neutralize special characters in values before it creates filters for dashboard and report requests. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.
Text from CVE List
Affected versions 7
- Splunk Enterpriseaffected: 10.4 before 10.4.4CVE List
- Splunk Enterpriseaffected: 10.2 before 10.2.8CVE List
- Splunk Enterpriseaffected: 10.0 before 10.0.11CVE List
- Splunk Enterpriseaffected: 9.4 before 9.4.16CVE List
- Splunk Secure Gatewayaffected: 3.10 before 3.10.12CVE List
- Splunk Secure Gatewayaffected: 3.9 before 3.9.26CVE List
- Splunk Secure Gatewayaffected: 3.8 before 3.8.73CVE List