CVE-2024-52973 json
Kibana allocation of resources without limits or throttling leads to crash
published last yr. modified 4mo ago also EUVD-2024-46266
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
An allocation of resources without limits or throttling in Kibana can lead to a crash caused by a specially crafted request to /api/log_entries/summary. This can be carried out by users with read access to the Observability-Logs feature in Kibana.
Patch / fix
- Elastic Kibana 7.17.23, 8.14.2
Is CVE-2024-52973 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
- last yr.
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-11).
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 |
Affected products
- Elastic Kibana
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
discuss.elastic.co
/t/kibana-7-17-23-and-8-14-2-security-update-esa-2024-26/373443
issue-tracking, patch, vendor-advisory
Sources
- CVE List CVE-2024-52973
- NVD CVE-2024-52973
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.