Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2024-52979

MEDIUM

CVE-2024-52979 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in org.elasticsearch:elasticsearch. O3 Security confirms whether CVE-2024-52979 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Elasticsearch Uncontrolled Resource Consumption vulnerability

Also known asBIT-elasticsearch-2024-52979GHSA-mm3m-5497-xggg
Published
May 1, 2025
Updated
Jul 15, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
org.elasticsearch:elasticsearchorg.elasticsearch:elasticsearch

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.elasticsearch:elasticsearchall versions7.17.25
Mavenorg.elasticsearch:elasticsearch8.0.0-alpha1&&< 8.16.08.16.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.elasticsearch:elasticsearch. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.elasticsearch:elasticsearch to 7.17.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52979 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-52979 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-52979. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-52979 in your dependencies?

O3 detects CVE-2024-52979 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.