CVSS: 5.2EPSS: 0%CPEs: 2EXPL: 0CVE-2023-49921
https://notcve.org/view.php?id=CVE-2023-49921
An issue was discovered by Elastic whereby Watcher search input logged the search query results on DEBUG log level. This could lead to raw contents of documents stored in Elasticsearch to be printed in logs. Elastic has released 8.11.2 and 7.17.16 that resolves this issue by removing this excessive logging. This issue only affects users that use Watcher and have a Watch defined that uses the search input and additionally have set the search input’s logger to DEBUG or finer, for example using: org.elasticsearch.xpack.watcher.input.search, org.elasticsearch.xpack.watcher.input, org.elasticsearch.xpack.watcher, or wider, since the loggers are hierarchical. • https://discuss.elastic.co/t/elasticsearch-8-11-2-7-17-16-security-update-esa-2023-29/349179 • CWE-532: Insertion of Sensitive Information into Log File •
CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-2024-23445 – Elasticsearch Remote Cluster Search Cross Cluster API Key insufficient restrictions
https://notcve.org/view.php?id=CVE-2024-23445
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 Se identificó que si se utiliza una clave API entre clústeres 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 restringe la búsqueda de un índice determinado utilizando la consulta o el parámetro field_security, y la misma clave API entre clústeres también otorga replicación para el mismo índice, las restricciones de búsqueda no se aplican durante las operaciones de búsqueda entre grupos y los resultados de la búsqueda pueden incluir documentos y términos que no deben devolverse. Este problema solo afecta el modelo de seguridad basado en clave API para clústeres remotos https://www.elastic.co/guide/en/elasticsearch/reference/8.14/remote-clusters.html#remote-clusters-security-models que anteriormente era un función beta y se lanza como GA con 8.14.0 • https://discuss.elastic.co/t/elasticsearch-8-14-0-security-update-esa-2024-13/360898 •
CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2024-23449 – Elasticsearch Uncaught Exception
https://notcve.org/view.php?id=CVE-2024-23449
An uncaught exception in Elasticsearch >= 8.4.0 and < 8.11.1 occurs when an encrypted PDF is passed to an attachment processor through the REST API. The Elasticsearch ingest node that attempts to parse the PDF file will crash. This does not happen with password-protected PDF files or with unencrypted PDF files. Se produce una excepción no detectada en Elasticsearch >= 8.4.0 y < 8.11.1 cuando se pasa un PDF cifrado a un procesador de archivos adjuntos a través de la API REST. El nodo de ingesta de Elasticsearch que intenta analizar el archivo PDF fallará. • https://discuss.elastic.co/t/elasticsearch-8-11-1-security-update-esa-2024-05/356458 • CWE-248: Uncaught Exception •
CVSS: 4.4EPSS: 0%CPEs: 1EXPL: 0CVE-2024-23451 – Elasticsearch Incorrect Authorization in the Remote Cluster Security API key based security model
https://notcve.org/view.php?id=CVE-2024-23451
Incorrect Authorization issue exists in the API key based security model for Remote Cluster Security, which is currently in Beta, in Elasticsearch 8.10.0 and before 8.13.0. This allows a malicious user with a valid API key for a remote cluster configured to use the new Remote Cluster Security to read arbitrary documents from any index on the remote cluster, and only if they use the Elasticsearch custom transport protocol to issue requests with the target index ID, the shard ID and the document ID. None of Elasticsearch REST API endpoints are affected by this issue. Existe un problema de autorización incorrecta en el modelo de seguridad basado en clave API para la seguridad de clúster remoto, que actualmente se encuentra en versión Beta, en Elasticsearch 8.10.0 y antes de 8.13.0. Esto permite que un usuario malintencionado con una clave API válida para un clúster remoto configurado para usar la nueva Seguridad de clúster remoto lea documentos arbitrarios de cualquier índice en el clúster remoto, y solo si utilizan el protocolo de transporte personalizado de Elasticsearch para emitir solicitudes con el ID del índice de destino, el ID del fragmento y el ID del documento. • https://discuss.elastic.co/t/elasticsearch-8-13-0-security-update-esa-2024-07/356315 • CWE-863: Incorrect Authorization •
CVSS: 4.9EPSS: 0%CPEs: 2EXPL: 0CVE-2024-23450 – Elasticsearch Uncontrolled Resource Consumption vulnerability
https://notcve.org/view.php?id=CVE-2024-23450
A flaw was discovered in Elasticsearch, where processing a document in a deeply nested pipeline on an ingest node could cause the Elasticsearch node to crash. Se descubrió una falla en Elasticsearch, donde el procesamiento de un documento en una canalización profundamente anidada en un nodo de ingesta podría provocar que el nodo Elasticsearch fallara. • https://discuss.elastic.co/t/elasticsearch-8-13-0-7-17-19-security-update-esa-2024-06/356314 https://security.netapp.com/advisory/ntap-20240517-0010 https://www.elastic.co/community/security • CWE-400: Uncontrolled Resource Consumption •