Unauthenticated Log Injection in Splunk Enterprise
Splunk Enterprise · Splunk Universal Forwarder
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Universal Forwarder |
| No fix yet |
Splunk Enterprise · Splunk Universal Forwarder
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Universal Forwarder |
| No fix yet |
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.
From the CVE record · Splunk
An attacker can inject ANSI escape codes into Splunk log files. If a user reads a malicious log file in a vulnerable terminal application that interprets those codes and performs additional interaction, the terminal application could potentially execute code; the products are not directly affected. Universal Forwarder is vulnerable in this scenario when its management services are active and accessible over the network, but not when they bind only to the local machine.
Check Splunk Enterprise versions below 9.1.0.2, 9.0.5.1, and 8.2.11.2, and Universal Forwarder versions 9.1.0.1, 9.0.5, 8.2.11, and lower where management services are network-accessible.