CVE-2023-31418

Elasticsearch uncontrolled resource consumption

Description

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.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.55%
Vendor Advisory elastic.co Vendor Advisory elastic.co
Affected: Elastic Elasticsearch
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2023-31418?
CVE-2023-31418 has been scored as a high severity vulnerability.
How to fix CVE-2023-31418?
To fix CVE-2023-31418, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2023-31418 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2023-31418 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-31418?
CVE-2023-31418 affects Elastic Elasticsearch.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.