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
Get an AI-powered plain-language explanation of this vulnerability and remediation steps.
Login to generate AI explanationCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
1 reference(s) from NVD