CVE-2024-52979 | Elasticsearch Uncontrolled Resource Consumption vulnerability

Uncontrolled Resource Consumption in Elasticsearch while evaluating specifically crafted search templates with Mustache functions can lead to Denial of Service by causing the Elasticsearch node to crash.

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

CVE-2024-52979 is rated Moderate Risk (40.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.20%). 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-52979

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-03-04 0.11% 0.20% +0.08%
2 2026-03-01 0.20% 0.11% -0.08%
3 2026-02-25 — 0.20% —

Full EPSS history (14 records total)

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

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-52979

GitHub Security Advisory for CVE-2024-52979

GHSA-mm3m-5497-xggg · Severity: medium · Ecosystem: maven — Elasticsearch Uncontrolled Resource Consumption Vulnerability

OS Trackers for CVE-2024-52979

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2024-52979
ubuntu medium CVE-2024-52979 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-52979

Affected software / configurations for CVE-2024-52979

Vendor Product Version Raw CPE
elastic elasticsearch < 7.17.25 cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*
elastic elasticsearch >= 8.0.0, < 8.16.0 cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*

References for CVE-2024-52979

cvelogic Threat Intelligence