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/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HElastic Cloud Enterprise
APPElastic3.6.0≤ 2.13.3Elastic Elasticsearch
APPElastic≤ 7.17.128.0.0 – 8.8.2
Related vulnerabilities
The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to by...
Elastic Cloud Enterprise — Server-Side Template Injection (SSTI) w silniku Jinjava
Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving...
The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers...
Improper Authorization in Elastic Cloud Enterprise can lead to Privilege Escalation where the built-in readonl...