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 true
Any 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
References
| Link | Resource |
|---|---|
| https://discuss.elastic.co/t/kibana-8-15-1-security-update-esa-2024-27-esa-2024-28/366119 | Patch Vendor Advisory |
Configurations
History
01 Oct 2025, 18:36
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:* | |
| First Time |
Elastic kibana
Elastic |
|
| References | () https://discuss.elastic.co/t/kibana-8-15-1-security-update-esa-2024-27-esa-2024-28/366119 - Patch, Vendor Advisory |
Information
Published : 2024-11-14 17:15
Updated : 2025-10-01 18:36
NVD link : CVE-2024-37285
Mitre link : CVE-2024-37285
CVE.ORG link : CVE-2024-37285
JSON object : View
Products Affected
elastic
- kibana
CWE
CWE-502
Deserialization of Untrusted Data
