Improperly Formatted ‘INGEST_EVAL’ Parameter Crashes Splunk Daemon
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
| No fix yet |
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 9.3.1, 9.2.3, and 9.1.6 and Splunk Cloud Platform versions below 9.2.2403.107, 9.1.2312.204, and 9.1.2312.111, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a search query with an improperly formatted "INGEST_EVAL" parameter as part of a [Field Transformation](https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Managefieldtransforms) which could crash the Splunk daemon (splunkd).
From the CVE record · Splunk
Affected Splunk Enterprise and Splunk Cloud Platform versions allow a low-privileged user without the admin or power role to crash the Splunk daemon. The user can do this by crafting a search query with an improperly formatted INGEST_EVAL parameter in a Field Transformation.
Teams running Splunk Enterprise below 9.3.1, 9.2.3, or 9.1.6, or Splunk Cloud Platform below 9.2.2403.107, 9.1.2312.204, or 9.1.2312.111, should check their deployments.