CVE-2024-36983 json
Command Injection using External Lookups
published 2y ago modified 4mo ago also EUVD-2024-36371
- cvss
- 8.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109 and 9.1.2308.207, an authenticated user could create an external lookup that calls a legacy internal function. The authenticated user could use this internal function to insert code into the Splunk platform installation directory. From there, the user could execute arbitrary code on the Splunk platform Instance.
Patch / fix
- Splunk Splunk Enterprise 9.0.10, 9.1.5, 9.2.2
- Splunk Splunk Cloud Platform 9.1.2308.207, 9.1.2312.109
- splunk splunk 9.0.10, 9.1.5, 9.2.2
- splunk splunk_cloud_platform 9.1.2308.207, 9.1.2312.109
Is CVE-2024-36983 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Splunk Splunk Enterprise
- Splunk Splunk Cloud Platform
- splunk splunk
- splunk splunk_cloud_platform
Classification
- Weakness
-
- CWE-77 Improper Neutralization of Special Elements used in a Command
References
-
advisory.splunk.com
/advisories/SVD-2024-0703
vendor-advisory
-
research.splunk.com
/application/1cf58ae1-9177-40b8-a26c-8966040f11ae/
tool-signature
Sources
- CVE List CVE-2024-36983
- NVD CVE-2024-36983
Fencer Intel 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.