CVE-2024-36990 json
Denial of Service (DoS) on the datamodel/web REST endpoint
published 2y ago modified 4mo ago also EUVD-2024-36377
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- 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.2.2403.100, an authenticated, low-privileged user that does not hold the admin or power Splunk roles could send a specially crafted HTTP POST request to the datamodel/web REST endpoint in Splunk Enterprise, potentially causing a denial of service.
Patch / fix
- Splunk Splunk Enterprise 9.0.10, 9.1.5, 9.2.2
- Splunk Splunk Cloud Platform 9.1.2308.209, 9.1.2312.109, 9.1.2312.202
Is CVE-2024-36990 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
- partial
- Assessed
- 2y ago
Exploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- research.splunk.com https://research.splunk.com/application/45766810-dbb2-44d4-b889-b4ba3ee0d1f5 referenced PoC, tagged "exploit" by a source, unverified
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
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
research.splunk.com
/application/45766810-dbb2-44d4-b889-b4ba3ee0d1f5
exploit, vendor-advisory
-
advisory.splunk.com
/advisories/SVD-2024-0710
vendor-advisory
Sources
- CVE List CVE-2024-36990
- NVD CVE-2024-36990
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.