Splunk has announced the release of security patches addressing vulnerabilities in its Enterprise product, focusing on flaws assigned a ‘high severity’ rating. Specifically, individual advisories have been issued for two high-severity vulnerabilities, including CVE-2024-29946, which affects the Dashboard Examples Hub in the Splunk Dashboard Studio app, potentially enabling attackers to bypass protections for risky Search Processing Language (SPL) commands. Another vulnerability, CVE-2024-29945, pertains to the potential exposure of authentication tokens during the token validation process, requiring local access to log files or admin access to internal indexes for exploitation.
Splunk elaborates that the CVE-2024-29946 vulnerability could be exploited by attackers phishing victims to initiate requests within their browsers, thereby bypassing SPL safeguards with highly-privileged user permissions. Meanwhile, CVE-2024-29945 exposes authentication tokens, primarily occurring when Splunk Enterprise runs in debug mode or JsonWebToken logging is configured at the DEBUG level, typically not the default settings. Although the company notes the necessity of local or admin access for exploitation, it underscores the criticality of promptly applying patches, mitigations, or workarounds provided.
Additionally, Splunk addresses several vulnerabilities introduced in Splunk Enterprise and Splunk Universal Forwarder due to third-party package usage, such as Curl, OpenSSL, and FasterXML’s Jackson. While issues affecting Universal Forwarder carry ‘low’ or ‘informational’ severity ratings, Enterprise vulnerabilities include both high and medium-severity flaws. Amidst growing cybersecurity threats, the availability of these patches and mitigations aims to bolster the security posture of Splunk deployments, safeguarding against potential exploitation by threat actors.
