CVE-2024-52973: Kibana allocation of resources without limits or throttling leads to crash
First published: Tue Jan 21 2025(Updated: )
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.
Credit: bressers@elastic.co
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Elastic |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-52973?
CVE-2024-52973 is classified with a critical severity due to its potential to cause system crashes.
How do I fix CVE-2024-52973?
To mitigate CVE-2024-52973, users should update to the latest version of Kibana where the vulnerability has been addressed.
What is the impact of CVE-2024-52973?
CVE-2024-52973 can lead to application crashes when specially crafted requests are sent to the Kibana API.
Who is affected by CVE-2024-52973?
Users with read access to the Observability-Logs feature in Kibana are affected by CVE-2024-52973.
What versions of Kibana are vulnerable to CVE-2024-52973?
CVE-2024-52973 affects multiple versions of Kibana, particularly those prior to the security updates.
- agent/title
- agent/references
- agent/weakness
- agent/type
- agent/first-publish-date
- agent/description
- collector/nvd-api
- source/NVD
- agent/severity
- agent/source
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/elastic
- canonical/elastic