{ "dataType": "CVE_RECORD", "dataVersion": "5.1", "cveMetadata": { "cveId": "CVE-2024-37285", "assignerOrgId": "271b6943-45a9-4f3a-ab4e-976f3fa05b5a", "state": "PUBLISHED", "assignerShortName": "elastic", "dateReserved": "2024-06-05T14:21:14.942Z", "datePublished": "2024-11-14T16:49:16.594Z", "dateUpdated": "2024-11-14T18:48:27.837Z" }, "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Kibana", "vendor": "Elastic", "versions": [ { "lessThanOrEqual": "8.15.0", "status": "affected", "version": "8.10.0", "versionType": "semver" } ] } ], "datePublic": "2024-09-05T15:42:00.000Z", "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "
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 and Kibana privileges assigned to them.
The following Elasticsearch indices permissions are required
write privilege on the system indices .kibana_ingest*allow_restricted_indices flag is set to trueAny of the following Kibana privileges are additionally required
Fleet the All privilege is grantedIntegration the Read or All privilege is grantedfleet-setup privilege is gained through the Fleet Server’s service account token