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

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.

Published: 2025-01-21 Last update: 2025-02-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-43709 is rated Moderate Risk (52.5/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.94%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-43709

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-25 1.23% 0.94% -0.29%
2 2026-05-24 0.90% 1.23% +0.33%
3 2026-03-04 — 0.90% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-43709

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2024-43709

GitHub Security Advisory for CVE-2024-43709

GHSA-jgx4-7v3v-vwfm · Severity: medium · Ecosystem: maven — Elasticsearch allocation of resources without limits or throttling leads to crash

OS Trackers for CVE-2024-43709

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2024-43709
ubuntu medium CVE-2024-43709 medium priority: Ubuntu including 1 source packages (elasticsearch), 8 status rows across 8 suites (focal, jammy, noble, oracular, plucky, questing, upstream, xenial): DNE 6, needs-triage 2. https://ubuntu.com/security/CVE-2024-43709

Affected software / configurations for CVE-2024-43709

Vendor Product Version Raw CPE
elastic elasticsearch >= 7.17.0, < 7.17.21 cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*
elastic elasticsearch >= 8.0.0, < 8.13.3 cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*

References for CVE-2024-43709

cvelogic Threat Intelligence