Rod Soto

**Name of the Vulnerable Software and Affected Versions** Splunk Enterprise versions prior to 9.3.1 Splunk Enterprise version 9.2.0 through 9.2.3 Splunk Cloud Platform versions prior to 9.2.2403.103 Splunk Cloud Platform versions 9.1.2312.200 through 9.1.2312.110 Splunk Cloud Platform version 9.1.2308.208 **Description** The issue is related to authorization procedure flaws in Splunk Enterprise, which could allow a low-privileged user without the "admin" or "power" Splunk roles to run a search as the "nobody" Splunk user in the SplunkDeploymentServerConfig app. This could let the low-privileged user access potentially restricted data. **Recommendations** For Splunk Enterprise versions prior to 9.3.1, update to version 9.3.1 or later. For Splunk Enterprise version 9.2.0 through 9.2.3, update to version 9.2.3 or later. For Splunk Cloud Platform versions prior to 9.2.2403.103, update to version 9.2.2403.103 or later. For Splunk Cloud Platform versions 9.1.2312.200 through 9.1.2312.110, update to a version outside of this range or later. For Splunk Cloud Platform version 9.1.2308.208, update to a version later than 9.1.2308.208. As a temporary workaround, consider restricting access to the SplunkDeploymentServerConfig app to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Splunk Enterprise versions prior to 9.3.1 Splunk Enterprise versions prior to 9.2.3 Splunk Enterprise versions prior to 9.1.6 **Description** The software potentially exposes sensitive HTTP parameters to the ` internal` index if the `REST Calls` log channel is configured at the DEBUG logging level. This issue is related to insufficient protection of service data, which could allow a remote attacker to gain unauthorized access to protected information. **Recommendations** For versions prior to 9.3.1, update to version 9.3.1 or later to resolve the issue. For versions prior to 9.2.3, update to version 9.2.3 or later to resolve the issue. For versions prior to 9.1.6, update to version 9.1.6 or later to resolve the issue. As a temporary workaround, consider configuring the `REST Calls` log channel at a logging level other than DEBUG to minimize the risk of sensitive HTTP parameter exposure.

Name of the Vulnerable Software and Affected Versions: Splunk Enterprise versions prior to 9.2.3 Splunk Enterprise versions prior to 9.1.6 Splunk Cloud Platform versions prior to 9.2.2403 Description: A low-privileged user without the "admin" or "power" Splunk roles could craft a malicious payload through Scheduled Views, potentially resulting in the execution of unauthorized JavaScript code in a user's browser. This issue is related to the lack of protection for the web page structure in the Splunk Web interface, which could allow a remote attacker to perform cross-site scripting attacks. Recommendations: For Splunk Enterprise versions prior to 9.2.3, update to version 9.2.3 or later to resolve the issue. For Splunk Enterprise versions prior to 9.1.6, update to version 9.1.6 or later to resolve the issue. For Splunk Cloud Platform versions prior to 9.2.2403, update to version 9.2.2403 or later to resolve the issue. As a temporary workaround, consider restricting access to Scheduled Views for low-privileged users until a patch is applied.

Name of the Vulnerable Software and Affected Versions: Splunk Enterprise versions prior to 9.3.1 Splunk Enterprise versions prior to 9.2.3 Splunk Enterprise versions prior to 9.1.6 Description: The software potentially exposes plaintext passwords for local native authentication Splunk users when the Splunk Enterprise AdminManager log channel is configured at the DEBUG logging level. This issue is related to insufficient protection of service data, which could allow a remote attacker to disclose protected information. Recommendations: For versions prior to 9.3.1, update to version 9.3.1 or later to resolve the issue. For versions prior to 9.2.3, update to version 9.2.3 or later to resolve the issue. For versions prior to 9.1.6, update to version 9.1.6 or later to resolve the issue. As a temporary workaround, consider avoiding the configuration of the Splunk Enterprise AdminManager log channel at the DEBUG logging level until a patch is available.