NVD / CVE Program· CNA elastic

CVE-2024-23450: Elasticsearch Uncontrolled Resource Consumption vulnerability

HighCVSS 7.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.8% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Elastic Elasticsearch 7.17.19, 8.13.0.
Severity is disputed: the assigning authority (CNA) scores it 4.9, NVD 7.5.

Low priority for now. Upgrade to Elastic Elasticsearch 7.17.19, 8.13.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A flaw was discovered in Elasticsearch, where processing a document in a deeply nested pipeline on an ingest node could cause the Elasticsearch node to crash.

Published: Mar 27, 2024
Updated: Jun 17, 2026
EPSS: 1.2% · 69th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.5
CNA · elastic: 4.9; 2.6 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
elastic	elasticsearch	cpe:2.3:a:elastic:elasticsearch

Versions reported by the vendor

Affected version ranges reported by the assigning authority (elastic). Independent of NVD's CPE analysis and usually ahead of it.

Elastic Elasticsearch
- 7.0.0 and later · before 7.17.19affected · semver
- 8.0.0 and later · before 8.13.0affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

elastic elasticsearch7.0.0 and later · before 7.17.19
elastic elasticsearch8.0.0 and later · before 8.13.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.elasticsearch:elasticsearch	from 7.0.0 · before 7.17.19	7.17.19
Maven	org.elasticsearch:elasticsearch	from 8.0.0 · before 8.13.0	8.13.0

Same product

elastic: all records

Other highest-scoring records for the same primary product.

CVE-2015-1427The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection…KEV
99Now
CVE-2014-3120The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL…KEV
89Now
CVE-2021-22145A memory disclosure vulnerability was identified in Elasticsearch 7.10.0 to 7.13.3 error reporting.
49Plan

Published before and after this one in the same product

← EarlierCVE-2023-46673Nov 22, 2023 · It was identified that malformed scripts used in the script processor of an Ingest Pipeline could cause an Elasticsearch node to crash when…
30Monitor
← EarlierCVE-2023-46674Dec 5, 2023 · Elasticsearch-hadoop Unsafe Deserialization
31Monitor
Later →CVE-2024-23451Mar 27, 2024 · Elasticsearch Incorrect Authorization in the Remote Cluster Security API key based security model
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Elastic Elasticsearch	7.17.19	Vendor (CNA)
Elastic Elasticsearch	8.13.0	Vendor (CNA)
Maven:org.elasticsearch:elasticsearch	7.17.19	Package registry (OSV)
Maven:org.elasticsearch:elasticsearch	8.13.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2023-31418153 days apartElasticsearch uncontrolled resource consumption
31Monitor
CVE-2024-52981377 days apartAn issue was discovered in Elasticsearch, where a large recursion using the Well-KnownText formatted string with nested GeometryCollection…
30Monitor
CVE-2024-52979400 days apartElasticsearch Uncontrolled Resource Consumption vulnerability
30Monitor
CVE-2024-52980377 days apartElasticsearch Uncontrolled Resource Consumption vulnerability
26Monitor

Bug bounty scope

ElasticHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

discuss.elastic.co/t/elasticsearch-8-13-0-7-17-19-security-update-esa-2024-06/356314

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records