The httplib and urllib Python libraries that Splunk shipped with Splunk Enterprise did not validate certificates using the certificate authority (CA) certificate stores by default in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203. Python 3 client libraries now verify server certificates by default and use the appropriate CA certificate stores for each library. Apps and add-ons that include their own HTTP libraries are not affected. For Splunk Enterprise, update to Splunk Enterprise version 9.0 and Configure TLS host name validation for Splunk-to-Splunk communications (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation) to enable the remediation.

In Splunk Enterprise and Universal Forwarder versions before 9.0, the Splunk command-line interface (CLI) did not validate TLS certificates while connecting to a remote Splunk platform instance by default. After updating to version 9.0, see Configure TLS host name validation for the Splunk CLI https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI to enable the remediation. The vulnerability does not affect the Splunk Cloud Platform. At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties. The issue requires conditions beyond the control of a potential bad actor such as a machine-in-the-middle attack. Hence, Splunk rates the complexity of the attack as High.

The Monitoring Console app configured in Distributed mode allows for a Reflected XSS in a query parameter in Splunk Enterprise versions before 8.1.4. The Monitoring Console app is a bundled app included in Splunk Enterprise, not for download on SplunkBase, and not installed on Splunk Cloud Platform instances. Note that the Cloud Monitoring Console is not impacted.

In Splunk Enterprise versions before 8.1.2, the uri path to load a relative resource within a web page is vulnerable to path traversal. It allows an attacker to potentially inject arbitrary content into the web page (e.g., HTML Injection, XSS) or bypass SPL safeguards for risky commands. The attack is browser-based. An attacker cannot exploit the attack at will and requires the attacker to initiate a request within the victim's browser (e.g., phishing).

When handling a mismatched pre-authentication cookie, the application leaks the internal error message in the response, which contains the Splunk Enterprise local system path. The vulnerability impacts Splunk Enterprise versions before 8.1.0.

A misconfiguration in the node default path allows for local privilege escalation from a lower privileged user to the Splunk user in Splunk Enterprise versions before 8.1.1 on Windows.

The Splunk Enterprise REST API allows enumeration of usernames via the lockout error message. The potential vulnerability impacts Splunk Enterprise instances before 8.1.7 when configured to repress verbose login errors.

A crafted request bypasses S2S TCP Token authentication writing arbitrary events to an index in Splunk Enterprise Indexer 8.1 versions before 8.1.5 and 8.2 versions before 8.2.1. The vulnerability impacts Indexers configured to use TCPTokens. It does not impact Universal Forwarders.

A potential vulnerability in Splunk Enterprise's implementation of DUO MFA allows for bypassing the MFA verification in Splunk Enterprise versions before 8.1.6. The potential vulnerability impacts Splunk Enterprise instances configured to use DUO MFA and does not impact or affect a DUO product or service.

The lack of validation of a key-value field in the Splunk-to-Splunk protocol results in a denial-of-service in Splunk Enterprise instances configured to index Universal Forwarder traffic. The vulnerability impacts Splunk Enterprise versions before 7.3.9, 8.0 versions before 8.0.9, and 8.1 versions before 8.1.3. It does not impact Universal Forwarders. When Splunk forwarding is secured using TLS or a Token, the attack requires compromising the certificate or token, or both. Implementation of either or both reduces the severity to Medium.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

The reserved CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used.