VulnerabilityModified
CVE-2023-31418
An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer.
HIGH 7.5EPSS 1.23%
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.23%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 1.23% probability · 67th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-400
- Affected
- elastic/elasticsearch · elastic/elastic cloud enterprise
- Source
- security@elastic.co
References
- https://discuss.elastic.co/t/elasticsearch-8-9-0-7-17-13-security-update/343616Vendor Advisory
- https://security.netapp.com/advisory/ntap-20231130-0005/
- https://www.elastic.co/community/securityVendor Advisory
- https://discuss.elastic.co/t/elasticsearch-8-9-0-7-17-13-security-update/343616Vendor Advisory
- https://security.netapp.com/advisory/ntap-20231130-0005/
- https://www.elastic.co/community/securityVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.