CVSS: 4.4EPSS: 0%CPEs: 2EXPL: 0CVE-2023-31417 – Elasticsearch Insertion of sensitive information in audit logs
https://notcve.org/view.php?id=CVE-2023-31417
Elasticsearch generally filters out sensitive information and credentials before logging to the audit log. It was found that this filtering was not applied when requests to Elasticsearch use certain deprecated URIs for APIs. The impact of this flaw is that sensitive information such as passwords and tokens might be printed in cleartext in Elasticsearch audit logs. Note that audit logging is disabled by default and needs to be explicitly enabled and even when audit logging is enabled, request bodies that could contain sensitive information are not printed to the audit log unless explicitly configured. Elasticsearch generalmente filtra la información y las credenciales confidenciales antes de iniciar sesión en el registro de auditoría. • https://discuss.elastic.co/t/elasticsearch-8-9-2-and-7-17-13-security-update/342479 https://security.netapp.com/advisory/ntap-20231130-0006 https://www.elastic.co/community/security • CWE-532: Insertion of Sensitive Information into Log File •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2023-31418 – Elasticsearch uncontrolled resource consumption
https://notcve.org/view.php?id=CVE-2023-31418
An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild. Se identificó un problema con la forma en que Elasticsearch manejó las solicitudes entrantes en la capa HTTP. Un usuario no autenticado podría forzar la salida de un nodo de Elasticsearch con un error OutOfMemory enviando una cantidad moderada de solicitudes HTTP con formato incorrecto. • https://discuss.elastic.co/t/elasticsearch-8-9-0-7-17-13-security-update/343616 https://security.netapp.com/advisory/ntap-20231130-0005 https://www.elastic.co/community/security • CWE-400: Uncontrolled Resource Consumption •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 2CVE-2023-31419 – Elasticsearch StackOverflow vulnerability
https://notcve.org/view.php?id=CVE-2023-31419
A flaw was discovered in Elasticsearch, affecting the _search API that allowed a specially crafted query string to cause a Stack Overflow and ultimately a Denial of Service. Se descubrió una falla en Elasticsearch que afectaba a la API _search y permitía que una cadena de consulta especialmente manipulada provocara un desbordamiento de pila y, en última instancia, una denegación de servicio. • https://github.com/sqrtZeroKnowledge/Elasticsearch-Exploit-CVE-2023-31419 https://github.com/u238/Elasticsearch-CVE-2023-31419 https://discuss.elastic.co/t/elasticsearch-8-9-1-7-17-13-security-update/343297 https://security.netapp.com/advisory/ntap-20231116-0010 https://www.elastic.co/community/security • CWE-121: Stack-based Buffer Overflow CWE-787: Out-of-bounds Write •
CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-2021-22147
https://notcve.org/view.php?id=CVE-2021-22147
Elasticsearch before 7.14.0 did not apply document and field level security to searchable snapshots. This could lead to an authenticated user gaining access to information that they are unauthorized to view. Elasticsearch versiones anteriores a 7.14.0, no aplicaba la seguridad a nivel de documento y de campo a las instantáneas con capacidad de búsqueda. Esto podía conllevar a que un usuario autenticado consiguiera acceso a información que no estaba autorizado a visualizar • https://discuss.elastic.co/t/elastic-stack-7-14-0-security-update/280344 https://security.netapp.com/advisory/ntap-20211008-0002 https://www.elastic.co/community/security • CWE-732: Incorrect Permission Assignment for Critical Resource CWE-862: Missing Authorization •
CVSS: 6.5EPSS: 0%CPEs: 3EXPL: 0CVE-2021-22144
https://notcve.org/view.php?id=CVE-2021-22144
In Elasticsearch versions before 7.13.3 and 6.8.17 an uncontrolled recursion vulnerability that could lead to a denial of service attack was identified in the Elasticsearch Grok parser. A user with the ability to submit arbitrary queries to Elasticsearch could create a malicious Grok query that will crash the Elasticsearch node. En Elasticsearch versiones anteriores a 7.13.3 y la 6.8.17, se ha identificado una vulnerabilidad de recursión no controlada que podía conllevar a un ataque de denegación de servicio en el analizador Grok de Elasticsearch. Un usuario con la capacidad de enviar consultas arbitrarias a Elasticsearch podría crear una consulta Grok maliciosa que bloquearía el nodo de Elasticsearch • https://discuss.elastic.co/t/elasticsearch-7-13-3-and-6-8-17-security-update/278100 https://security.netapp.com/advisory/ntap-20210827-0006 https://www.oracle.com/security-alerts/cpuapr2022.html • CWE-674: Uncontrolled Recursion •