Log Injection through the REST API in Splunk App for Splunk O11y Cloud
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Enterprise 10.0.10, Enterprise 10.2.7 and Enterprise 10.4.3.
In Splunk Enterprise versions below 10.4.3, 10.2.7, and 10.0.10, a user that holds a role with the read_o11y_content capability could inject forged entries into the app log through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk App for Splunk O11y Cloud does not neutralize user-supplied SignalFlow content before writing it to the app log. Splunk Enterprise versions 9.4.x are not affected.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Splunk | Enterprise | >=10.0 <10.0.10, >=10.2 <10.2.7, >=10.4 <10.4.3 | 10.0.10, 10.2.7, 10.4.3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Enterprise, strongest first
Embed
A live severity badge for an advisory, README or ticket