CVE-2024-43708
First published: Thu Jan 23 2025(Updated: )
An allocation of resources without limits or throttling in Kibana can lead to a crash caused by a specially crafted payload to a number of inputs in Kibana UI. This can be carried out by users with read access to any 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-43708?
CVE-2024-43708 has been classified with high severity due to its potential to cause crashes in Kibana.
How do I fix CVE-2024-43708?
To fix CVE-2024-43708, you should update Kibana to the latest version where the vulnerability has been addressed.
Who is affected by CVE-2024-43708?
CVE-2024-43708 affects users with read access to any feature in Kibana.
What types of attacks can exploit CVE-2024-43708?
CVE-2024-43708 can be exploited through specially crafted payloads sent to various inputs within the Kibana UI.
Is there a workaround for CVE-2024-43708 before the fix is applied?
There are currently no recommended workarounds for CVE-2024-43708, so upgrading is the best option.
- agent/weakness
- agent/references
- agent/description
- agent/first-publish-date
- agent/type
- 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