Skip to content
Fencer Intel
medium 4.9

CVE-2024-37280 json

Elasticsearch StackOverflow vulnerability

published 2y ago modified 2mo ago also BIT-elasticsearch-2024-37280 , EUVD-2024-1914 , GHSA-4q22-422g-m4pj

cvss
4.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

A flaw was discovered in Elasticsearch, affecting document ingestion when an index template contains a dynamic field mapping of “passthrough” type. Under certain circumstances, ingesting documents in this index would cause a StackOverflow exception to be thrown and ultimately lead to a Denial of Service. Note that passthrough fields is an experimental feature.

Patch / fix

  • maven org.elasticsearch:elasticsearch 8.14.0
  • bitnami elasticsearch 8.14.0
  • elastic elasticsearch 8.14.0
  • elasticsearch elasticsearch 8.14.0
  • org.elasticsearch elasticsearch 8.14.0

Is CVE-2024-37280 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-37280 updated cvss 4.9

elasticsearch: Ingesting documents in this index would cause a StackOverflow exception

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/fluentd-rhel8, openshift-logging/kibana6-rhel8 Red Hat OpenStack Platform 16.1 python3-panko, openstack-panko-api, openstack-panko-common Red Hat OpenStack Platform 16.2 python3-panko, openstack-panko-api, openstack-panko-common Red Hat Quay 3 quay/quay-rhel8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
>=8.13.1, <8.14.0
8.14.0
bitnami elasticsearch
>=8.13.1, <8.14.0
8.14.0

Affected products

  • Elastic Elasticsearch

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.