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

CVE-2024-43709 · Severity: low · CVSS 3.1 · Published 2025-01-21

Elasticsearch allocation of resources without limits or throttling leads to crash

Technologies: org.elasticsearch:elasticsearch (Maven). Vendors: Maven.

Quick answers

Is CVE-2024-43709 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-43709 being exploited in the wild.
How severe is CVE-2024-43709?
Low severity, with a CVSS score of 3.1, published 21 January 2025.
Which products and versions are affected?
org.elasticsearch:elasticsearch (Maven) ECOSYSTEM:introduced=0,fixed=7.17.21.
Is there a fix for CVE-2024-43709?
Yes. org.elasticsearch:elasticsearch (Maven): upgrade to 7.17.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-43709?
Check whether you run org.elasticsearch:elasticsearch (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.elasticsearch:elasticsearch (Maven): upgrade to 7.17.21 or later
    # set org.elasticsearch:elasticsearch to 7.17.21 in your pom.xml or build.gradle

Affected products

  • org.elasticsearch:elasticsearch (Maven) ECOSYSTEM:introduced=0,fixed=7.17.21

Identifiers

  • CVE-2024-43709
  • GHSA-jgx4-7v3v-vwfm

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.