Page 16 of 158 results (0.036 seconds)

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

A document disclosure flaw was found in Elasticsearch versions after 7.6.0 and before 7.11.0 when Document or Field Level Security is used. Get requests do not properly apply security permissions when executing a query against a recently updated document. This affects documents that have been updated and not yet refreshed in the index. This could result in the search disclosing the existence of documents and fields the attacker should not be able to view. Se encontró un fallo en una divulgación de documentos en Elasticsearch versiones posteriores a 7.6.0 y versiones anteriores a 7.11.0, cuando es usada el Nivel de Seguridad de Documento o Campo. • https://discuss.elastic.co/t/elastic-stack-7-11-0-security-update/265835 https://security.netapp.com/advisory/ntap-20210430-0006 https://www.oracle.com/security-alerts/cpuapr2022.html • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-863: Incorrect Authorization •

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

The Elastic APM agent for Go versions before 1.11.0 can leak sensitive HTTP header information when logging the details during an application panic. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application panic it is possible the headers will not be sanitized before being sent. El agente de Elastic APM para Go versiones anteriores a 1.11.0, puede filtrar información confidencial del encabezado HTTP al registrar los detalles durante un pánico en la aplicación. Normalmente, el agente de APM se saneará en los detalles del encabezado HTTP confidenciales antes de enviar la información al servidor de APM. • https://discuss.elastic.co/t/elastic-apm-agent-for-go-1-11-0-security-update/263252 https://access.redhat.com/security/cve/CVE-2021-22133 https://bugzilla.redhat.com/show_bug.cgi?id=1942553 • CWE-532: Insertion of Sensitive Information into Log File •

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

Elasticsearch versions before 7.10.0 and 6.8.14 have an information disclosure issue when audit logging and the emit_request_body option is enabled. The Elasticsearch audit log could contain sensitive information such as password hashes or authentication tokens. This could allow an Elasticsearch administrator to view these details. Las versiones de Elasticsearch versiones anteriores a 7.10.0 y 6.8.14, presentan un problema de divulgación de información cuando se habilita el registro de auditoría y la opción emit_request_body. El registro de auditoría de Elasticsearch podría contener información confidencial como un hash de contraseña o tokens de autenticación. • https://discuss.elastic.co/t/elastic-stack-7-11-0-and-6-8-14-security-update/263915 https://security.netapp.com/advisory/ntap-20210319-0003 • CWE-532: Insertion of Sensitive Information into Log File •

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

Elasticsearch versions 7.7.0 to 7.10.1 contain an information disclosure flaw in the async search API. Users who execute an async search will improperly store the HTTP headers. An Elasticsearch user with the ability to read the .tasks index could obtain sensitive request headers of other users in the cluster. This issue is fixed in Elasticsearch 7.10.2 Elasticsearch versiones 7.7.0 hasta 7.10.1, contienen un fallo de divulgación de información en la API de búsqueda asíncrona. Los usuarios que ejecutan una búsqueda asíncrona almacenarán inapropiadamente los encabezados HTTP. • https://discuss.elastic.co/t/elasticsearch-7-10-2-security-update/261164 https://security.netapp.com/advisory/ntap-20210219-0004 https://www.oracle.com/security-alerts/cpuapr2022.html https://access.redhat.com/security/cve/CVE-2021-22132 https://bugzilla.redhat.com/show_bug.cgi?id=1923181 • CWE-522: Insufficiently Protected Credentials •

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

The elasticsearch-operator does not validate the namespace where kibana logging resource is created and due to that it is possible to replace the original openshift-logging console link (kibana console) to different one, created based on the new CR for the new kibana resource. This could lead to an arbitrary URL redirection or the openshift-logging console link damage. This flaw affects elasticsearch-operator-container versions before 4.7. Elasticsearch-operator no comprueba el espacio de nombres donde el recurso de registro de kibana es creado y, debido a eso, es posible reemplazar el enlace de la consola de registro de openshift original (consola de kibana) por uno diferente, creado en base al nuevo CR para el nuevo recurso de kibana. Esto podría conllevar al redireccionamiento de una URL arbitraria o daños en el enlace de la consola de registro de openshift. • https://bugzilla.redhat.com/show_bug.cgi?id=1902698 https://access.redhat.com/security/cve/CVE-2020-27816 • CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •