Use of Hard-coded Cryptographic Key through Companion App Registration in Splunk Secure Gateway
Splunk Enterprise · Splunk Secure Gateway
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Secure Gateway |
|
Splunk Enterprise · Splunk Secure Gateway
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Secure Gateway |
|
| No fix yet |
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.10, 3.9.24, and 3.8.71, a user who does not hold the "admin" or "power" Splunk roles could register an arbitrary companion app and cause Splunk Secure Gateway to forward mobile user requests, including tokens that compromise all relevant data available to the affected mobile user, to an attacker-controlled Uniform Resource Locator (URL). The vulnerability is possible because a hard-coded cryptographic key in the Splunk Secure Gateway companion app registration handler allows for arbitrary callback URL registration without restriction. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
From the CVE record · cisco
A hard-coded cryptographic key in the Splunk Secure Gateway companion app registration handler allows arbitrary callback URL registration. A Splunk user without the admin or power role could register a companion app that forwards mobile user requests and tokens to an attacker-controlled URL, potentially compromising data available to those mobile users.
Teams running Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, or 9.4.14, or Splunk Secure Gateway versions below 3.10.10, 3.9.24, or 3.8.71, should check their deployments.