CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-2024-23446 – Kibana Broken Access Control issue
https://notcve.org/view.php?id=CVE-2024-23446
An issue was discovered by Elastic, whereby the Detection Engine Search API does not respect Document-level security (DLS) or Field-level security (FLS) when querying the .alerts-security.alerts-{space_id} indices. Users who are authorized to call this API may obtain unauthorized access to documents if their roles are configured with DLS or FLS against the aforementioned index. Elastic descubrió un problema por el cual la API de búsqueda del motor de detección no respeta la seguridad a nivel de documento (DLS) o la seguridad a nivel de campo (FLS) al consultar los índices .alerts-security.alerts-{space_id}. Los usuarios que estén autorizados a llamar a esta API pueden obtener acceso no autorizado a documentos si sus roles están configurados con DLS o FLS contra el índice antes mencionado. • https://discuss.elastic.co/t/kibana-8-12-1-security-update-esa-2024-01/352686 https://www.elastic.co/community/security • CWE-284: Improper Access Control •
CVSS: 8.0EPSS: 0%CPEs: 2EXPL: 0CVE-2023-46675 – Kibana Insertion of Sensitive Information into Log File
https://notcve.org/view.php?id=CVE-2023-46675
An issue was discovered by Elastic whereby sensitive information may be recorded in Kibana logs in the event of an error or in the event where debug level logging is enabled in Kibana. Elastic has released Kibana 8.11.2 which resolves this issue. The messages recorded in the log may contain Account credentials for the kibana_system user, API Keys, and credentials of Kibana end-users, Elastic Security package policy objects which can contain private keys, bearer token, and sessions of 3rd-party integrations and finally Authorization headers, client secrets, local file paths, and stack traces. The issue may occur in any Kibana instance running an affected version that could potentially receive an unexpected error when communicating to Elasticsearch causing it to include sensitive data into Kibana error logs. It could also occur under specific circumstances when debug level logging is enabled in Kibana. • https://discuss.elastic.co/t/kibana-8-11-2-7-17-16-security-update-esa-2023-27/349182/2 • CWE-532: Insertion of Sensitive Information into Log File •
CVSS: 8.0EPSS: 0%CPEs: 1EXPL: 0CVE-2023-46671 – Kibana Insertion of Sensitive Information into Log File
https://notcve.org/view.php?id=CVE-2023-46671
An issue was discovered by Elastic whereby sensitive information may be recorded in Kibana logs in the event of an error. Elastic has released Kibana 8.11.1 which resolves this issue. The error message recorded in the log may contain account credentials for the kibana_system user, API Keys, and credentials of Kibana end-users. The issue occurs infrequently, only if an error is returned from an Elasticsearch cluster, in cases where there is user interaction and an unhealthy cluster (for example, when returning circuit breaker or no shard exceptions). Elastic descubrió un problema por el cual se puede registrar información confidencial en los registros de Kibana en caso de un error. • https://discuss.elastic.co/t/8-11-1-7-17-15-security-update-esa-2023-25/347149 • CWE-532: Insertion of Sensitive Information into Log File •
CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 0CVE-2023-6687 – Elastic Agent Insertion of Sensitive Information into Log File
https://notcve.org/view.php?id=CVE-2023-6687
An issue was discovered by Elastic whereby Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Elastic Agent logs. Elastic has released 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default. Elastic descubrió un problema por el cual Elastic Agent registraba un evento sin formato en sus propios registros en el nivel WARN o ERROR si fallaba la ingesta de ese evento en Elasticsearch con cualquier código de estado HTTP 4xx excepto 409 o 429. Dependiendo de la naturaleza del evento, el Agente Elástico intentó ingerir, esto podría llevar a la inserción de información confidencial o privada en los registros del Agente Elástico. • https://discuss.elastic.co/t/beats-and-elastic-agent-8-11-3-7-17-16-security-update-esa-2023-30/349180 • CWE-532: Insertion of Sensitive Information into Log File •
CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 0CVE-2023-49922 – Beats Insertion of Sensitive Information into Log File
https://notcve.org/view.php?id=CVE-2023-49922
An issue was discovered by Elastic whereby Beats and Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Beats or Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Beats or Elastic Agent logs. Elastic has released 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default. Elastic descubrió un problema por el cual Beats y Elastic Agent registraban un evento sin procesar en sus propios registros en el nivel WARN o ERROR si fallaba la ingesta de ese evento en Elasticsearch con cualquier código de estado HTTP 4xx excepto 409 o 429. Dependiendo de la naturaleza del en caso de que Beats o Elastic Agent intentaran ingerir, esto podría dar lugar a la inserción de información confidencial o privada en los registros de Beats o Elastic Agent. • https://discuss.elastic.co/t/beats-and-elastic-agent-8-11-3-7-17-16-security-update-esa-2023-30/349180 • CWE-532: Insertion of Sensitive Information into Log File •