Page 6 of 158 results (0.007 seconds)

CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0

The Elastic APM .NET Agent can leak sensitive HTTP header information when logging the details during an application error. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application error it is possible the headers will not be sanitized before being sent. Elastic APM .NET Agent puede filtrar información confidencial del encabezado HTTP al registrar los detalles durante un error de la aplicación. Normalmente, el agente de APM sanitizará los detalles confidenciales del encabezado HTTP antes de enviar la información al servidor de APM. • https://discuss.elastic.co/t/elastic-apm-net-agent-1-10-0-security-update/274668 https://www.elastic.co/community/security • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-532: Insertion of Sensitive Information into Log File •

CVSS: 8.8EPSS: 0%CPEs: 1EXPL: 0

Kibana contains an embedded version of the Chromium browser that the Reporting feature uses to generate the downloadable reports. If a user with permissions to generate reports is able to render arbitrary HTML with this browser, they may be able to leverage known Chromium vulnerabilities to conduct further attacks. Kibana contains a number of protections to prevent this browser from rendering arbitrary content. Kibana contiene una versión integrada del navegador Chromium que la función de informes utiliza para generar informes descargables. Si un usuario con permisos para generar informes puede representar HTML arbitrario con este navegador, es posible que pueda aprovechar las vulnerabilidades conocidas de Chromium para realizar más ataques. • https://discuss.elastic.co/t/elastic-stack-7-13-0-and-6-8-16-security-update/273964/1 https://www.elastic.co/community/security • CWE-1104: Use of Unmaintained Third Party Components •

CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0

It was discovered that Kibana was not validating a user supplied path, which would load .pbf files. Because of this, a malicious user could arbitrarily traverse the Kibana host to load internal files ending in the .pbf extension. Se descubrió que Kibana no estaba validando una ruta proporcionada por el usuario, que cargaría archivos .pbf. Debido a esto, un usuario malintencionado podría atravesar arbitrariamente el host de Kibana para cargar archivos internos que terminen en la extensión .pbf. • https://discuss.elastic.co/t/elastic-stack-7-14-1-security-update/283077 https://www.elastic.co/community/security • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •

CVSS: 7.2EPSS: 0%CPEs: 1EXPL: 0

It was discovered that a user with Fleet admin permissions could upload a malicious package. Due to using an older version of the js-yaml library, this package would be loaded in an insecure manner, allowing an attacker to execute commands on the Kibana server. Se descubrió que un usuario con permisos de administrador Fleet podía cargar un paquete malicioso. Debido al uso de una versión anterior de la librería js-yaml, este paquete se cargaría de forma insegura, lo que permitiría a un atacante ejecutar comandos en el servidor Kibana. • https://discuss.elastic.co/t/elastic-stack-7-14-1-security-update/283077 https://www.elastic.co/community/security • CWE-94: Improper Control of Generation of Code ('Code Injection') •

CVSS: 8.4EPSS: 0%CPEs: 2EXPL: 0

An issue was identified by Elastic whereby sensitive information is recorded in Logstash logs under specific circumstances. The prerequisites for the manifestation of this issue are: * Logstash is configured to log in JSON format https://www.elastic.co/guide/en/logstash/current/running-logstash-command-line.html , which is not the default logging format. * Sensitive data is stored in the Logstash keystore and referenced as a variable in Logstash configuration. Elastic identificó un problema por el cual se registra información confidencial en los registros de Logstash en circunstancias específicas. Los requisitos previos para la manifestación de este problema son: * Logstash está configurado para iniciar sesión en formato JSON https://www.elastic.co/guide/en/logstash/current/running-logstash-command-line.html, que no es el formato de registro predeterminado. * Los datos confidenciales se almacenan en el almacén de claves de Logstash y se hace referencia a ellos como una variable en la configuración de Logstash. • https://discuss.elastic.co/t/logstash-8-11-1-security-update-esa-2023-26/347191 https://security.netapp.com/advisory/ntap-20240125-0002 https://security.netapp.com/advisory/ntap-20240229-0001 https://www.elastic.co/community/security • CWE-532: Insertion of Sensitive Information into Log File •