CVE-2024-45736 json
Improperly Formatted ‘INGEST_EVAL’ Parameter Crashes Splunk Daemon
published 2024-10-14 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-41738
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
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).
Patch / fix
- Splunk Splunk Enterprise 9.1.6, 9.2.3, 9.3.1
- Splunk Splunk Cloud Platform 9.1.2312.111, 9.1.2312.204, 9.2.2403.107
- splunk splunk_enterprise 9.1.6, 9.2.3, 9.3.1
- splunk splunk_cloud_platform 9.1.2312.111, 9.1.2312.204, 9.2.2403.107
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Splunk Splunk Enterprise
- Splunk Splunk Cloud Platform
- splunk splunk_enterprise
- splunk splunk_cloud_platform
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
advisory.splunk.com
/advisories/SVD-2024-1006
vendor-advisory
-
research.splunk.com
/application/08978eca-caff-44c1-84dc-53f17def4e14/
vendor-advisory
Sources
- CVE List CVE-2024-45736
- NVD CVE-2024-45736
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.