The native inference process that Elasticsearch uses to evaluate uploaded machine learning models accepts a model operation that computes a memory address from an offset supplied inside the model, without validating that the offset stays within the bounds of the underlying storage. A user with the privileges required to upload and deploy a trained model can craft a model that reads and writes memory outside the intended allocation. The result is heap corruption that crashes the inference process, and, with sufficient control over the heap layout, could allow arbitrary code execution in the context of that process.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HElastic Elasticsearch
APPElastic8.19.0 – 8.19.20 (excl.)9.4.0 – 9.4.5 (excl.)9.5.0 – 9.5.1 (excl.)
Related vulnerabilities
Elasticsearch: ucieczka z sandboksa Groovy i zdalne wykonanie poleceń
RCE w Elasticsearch przez protokół transportowy (przed wersją 1.6.1)
The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers...
Deserialization of Untrusted Data (CWE-502) in the Elasticsearch machine learning component can lead to remote...
An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenti...