### [CVE-2024-37285](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37285)
![](https://img.shields.io/static/v1?label=Product&message=Kibana&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=8.10.0%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-502%20Deserialization%20of%20Untrusted%20Data&color=brightgreen)

### Description

A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document containing a crafted payload. A successful attack requires a malicious user to have a combination of both specific  Elasticsearch indices privileges https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html#roles-indices-priv  and  Kibana privileges https://www.elastic.co/guide/en/fleet/current/fleet-roles-and-privileges.html  assigned to them.The following Elasticsearch indices permissions are required  *  write privilege on the system indices .kibana_ingest*  *  The allow_restricted_indices flag is set to trueAny of the following Kibana privileges are additionally required  *  Under Fleet the All privilege is granted  *  Under Integration the Read or All privilege is granted  *  Access to the fleet-setup privilege is gained through the Fleet Server’s service account token

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/Threekiii/CVE