Deserialization in Elastic Kibana
CVE-2024-37285
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
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.1 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.012, 69.8th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Elastic Kibana — versions 8.10.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (Threekiii/CVE). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- discuss.elastic.co/t/kibana-8-15-1-security-update-esa-2024-27-esa-2024-28/3661… (Patch, Vendor Advisory)