CVE-2023-31418: Elasticsearch uncontrolled resource consumption
Elastic · Elasticsearch
Vendor fix available · Affected: Elasticsearch · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 81% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Elastic · Elasticsearch7.17.12; from 8.0.0 before 8.8.2; from 2.13.3 before 3.6.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Elastic
- Published
- October 2023
CoverageNo articles yet
No CyberSIXT article names CVE-2023-31418 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.