Unauthenticated Log Injection in Splunk Enterprise

Summary

In Splunk Enterprise versions below 9.1.0.2, 9.0.5.1, and 8.2.11.2, an attacker can inject American National Standards Institute (ANSI) escape codes into Splunk log files that, when a vulnerable terminal application reads them, can potentially, at worst, result in possible code execution in the vulnerable application. This attack requires a user to use a terminal application that supports the translation of ANSI escape codes to read the malicious log file locally in the vulnerable terminal, and to perform additional user interaction to exploit. Universal Forwarder versions 9.1.0.1, 9.0.5, 8.2.11, and lower can be vulnerable in situations where they have management services active and accessible over the network. Universal Forwarder versions 9.0.x and 9.1.x bind management services to the local machine and are not vulnerable in this specific configuration. See SVD-2022-0605 for more information. Universal Forwarder versions 9.1 use Unix Domain Sockets (UDS) for communication, which further reduces the potential attack surface. The vulnerability does not directly affect Splunk Enterprise or Universal Forwarder. The indirect impact on Splunk Enterprise and Universal Forwarder can vary significantly depending on the permissions in the vulnerable terminal application and where and how the user reads the malicious log file. For example, users can copy the malicious file from the Splunk Enterprise instance and read it on their local machine.

Timeline

1. Jun 1, 2023, 4:34 PM UTCCVE published
2. May 20, 2024, 7:25 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Feb 28, 2025, 11:03 AM UTCRecord last updated

Affected versions

• Splunk Splunk Enterprise

  From 8.2 · fixed in 8.2.11.2; From 9.0 · fixed in 9.0.5.1; From 9.1 · fixed in 9.1.0.2

• Splunk Universal Forwarder

  From 8.2 · fixed in 8.2.12; From 9.0 · fixed in 9.0.6; From 9.1 · fixed in 9.1.1

References 2