First published: Thu Nov 14 2024(Updated: )
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
Credit: bressers@elastic.co
Affected Software | Affected Version | How to fix |
---|---|---|
Elastic |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-37285 has a high severity rating due to the potential for arbitrary code execution.
To mitigate CVE-2024-37285, upgrade Kibana to the latest security patch provided by Elastic.
CVE-2024-37285 is a deserialization vulnerability that affects Kibana.
A successful exploitation of CVE-2024-37285 requires specific Elasticsearch indices privileges by a malicious user.
CVE-2024-37285 affects Elastic Kibana across unspecified versions.