First published: Thu Oct 26 2023(Updated: )
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.
Credit: bressers@elastic.co bressers@elastic.co
Affected Software | Affected Version | How to fix |
---|---|---|
Elastic Elasticsearch | <=7.17.12 | |
Elastic Elasticsearch | >=8.0.0<=8.8.2 | |
Elastic Elastic Cloud Enterprise | <=2.13.3 | |
Elastic Elastic Cloud Enterprise | =3.6.0 | |
maven/org.elasticsearch:elasticsearch | >=8.0.0<8.9.0 | 8.9.0 |
maven/org.elasticsearch:elasticsearch | <7.17.13 | 7.17.13 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2023-31418.
The severity of CVE-2023-31418 is high with a score of 7.5.
Elasticsearch versions 8.0.0 up to and including 8.9.0, and version 7.17.13 are affected by CVE-2023-31418.
An unauthenticated user can force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests.
You can find more information about CVE-2023-31418 on the Elastic community security page, the NIST National Vulnerability Database (NVD) page, and the provided references.