CVE-2023-31418 json
Elasticsearch uncontrolled resource consumption
published 2023-10-26 3 y ago modified 2026-09-10 1 mo ago also BIT-elasticsearch-2023-31418 , EUVD-2023-2618 , GHSA-2cqf-6xv9-f22w
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.
Patch / fix
- maven org.elasticsearch:elasticsearch 7.17.13, 8.9.0
- bitnami elasticsearch 7.17.13, 8.8.3
- Elastic Elasticsearch 3.6.0, 8.8.2
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-2023-31418 updated cvss 7.5
elasticsearch: uncontrolled resource consumption
-
Red Hat JBoss Fuse Service Works 6 elasticsearchaffected: no fix planned “Out of support scope”
-
Red Hat Quay 3 quay/quay-rhel8affected: no fix available
-
Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/fluentd-rhel8, openshift-logging/kibana6-rhel8, openshift-logging/elasticsearch6-rhel8not 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
Exploit prediction
2.05% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.elasticsearch:elasticsearch | <7.17.13 >=8.0.0, <8.9.0 |
7.17.13 8.9.0 |
| bitnami | elasticsearch | <7.17.13 >=8.0.0, <8.8.3 |
7.17.13 8.8.3 |
Affected products
- Elastic Elasticsearch
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
discuss.elastic.co
/t/elasticsearch-8-9-0-7-17-13-security-update/343616
web, vendor-advisory, advisory
-
elastic.co
/community/security
web, vendor-advisory, advisory
-
security.netapp.com
/advisory/ntap-20231130-0005/
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-31418
advisory, web
-
security.netapp.com
/advisory/ntap-20231130-0005
web
Sources
- CVE List CVE-2023-31418
- GitHub Advisory GHSA-2cqf-6xv9-f22w
- NVD CVE-2023-31418
- OSV BIT-elasticsearch-2023-31418
Fencer Vulns 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.