CVE-2023-31418GHSA-2CQF-6XV9-F22WBIT-ELASTICSEARCH-2023-31418
Elasticsearch uncontrolled resource consumption
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.8.2, 3.6.0, 7.17.13, 8.9.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Elastic Elasticsearch
From 8.0.0 · fixed in 8.8.2; From 2.13.3 · fixed in 3.6.0
- org.elasticsearch:elasticsearchMaven
fixed in 7.17.13
- org.elasticsearch:elasticsearchMaven
From 8.0.0 · fixed in 8.9.0