Unauthenticated Log Injection in Splunk Enterprise
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
Splunk Enterprise · Splunk Cloud Platform
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
| No fix yet |
In Splunk Enterprise versions below 10.0.1, 9.4.6, 9.3.8, and 9.2.10, and Splunk Cloud Platform versions below 10.1.2507.4, 10.0.2503.6, and 9.3.2411.117.125, an unauthenticated attacker can inject American National Standards Institute (ANSI) escape codes into Splunk log files due to improper validation at the /en-US/static/ web endpoint. This may allow them to poison, forge, or obfuscate sensitive log data through specially crafted HTTP requests, potentially impacting log integrity and detection capabilities.
From the CVE record · cisco
The /en-US/static/ web endpoint improperly validates input in affected Splunk Enterprise and Splunk Cloud Platform versions. An unauthenticated attacker can send crafted HTTP requests that inject ANSI escape codes into log files, potentially poisoning, forging, or obscuring log data.
Teams running Splunk Enterprise below 10.0.1, 9.4.6, 9.3.8, or 9.2.10, or Splunk Cloud Platform below 10.1.2507.4, 10.0.2503.6, or 9.3.2411.117.125, should check their deployments.