CVE-2024-23445 json
Elasticsearch Remote Cluster Search Cross Cluster API Key insufficient restrictions
published 2024-06-12 2 y ago modified 2026-09-08 2 mo ago also BIT-elasticsearch-2024-23445 , EUVD-2024-20948
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
It was identified that if a cross-cluster API key https://www.elastic.co/guide/en/elasticsearch/reference/8.14/security-api-create-cross-cluster-api-key.html#security-api-create-cross-cluster-api-key-request-body restricts search for a given index using the query or the field_security parameter, and the same cross-cluster API key also grants replication for the same index, the search restrictions are not enforced during cross cluster search operations and search results may include documents and terms that should not be returned.
This issue only affects the API key based security model for remote clusters https://www.elastic.co/guide/en/elasticsearch/reference/8.14/remote-clusters.html#remote-clusters-security-models that was previously a beta feature and is released as GA with 8.14.0
Patch / fix
- bitnami elasticsearch 8.14.0
- Elastic Elasticsearch 8.14.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-23445 updated cvss 6.5
elasticsearch: Remote Cluster Search Cross Cluster API Key insufficient restrictions
-
Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/fluentd-rhel8, openshift-logging/kibana6-rhel8 Red Hat OpenStack Platform 16.1 python3-panko, openstack-panko-api, openstack-panko-common Red Hat OpenStack Platform 16.2 python3-panko, openstack-panko-api, openstack-panko-common Red Hat Quay 3 quay/quay-rhel8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | elasticsearch | >=8.10.0, <8.14.0 |
8.14.0 |
Affected products
- Elastic Elasticsearch
Classification
- Weakness
-
- CWE-922 Insecure Storage of Sensitive Information
References
Sources
- CVE List CVE-2024-23445
- NVD CVE-2024-23445
- OSV BIT-elasticsearch-2024-23445
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.