CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0CVE-2023-31416 – Elastic Cloud on Kubernetes (ECK) secret token configuration issue
https://notcve.org/view.php?id=CVE-2023-31416
Secret token configuration is never applied when using ECK <2.8 with APM Server >=8.0. This could lead to anonymous requests to an APM Server being accepted and the data ingested into this APM deployment. La configuración del token secreto nunca se aplica cuando se usa ECK <2.8 con APM Server>=8.0. Esto podría dar lugar a que se acepten solicitudes anónimas a un servidor APM y que los datos se ingieran en esta implementación de APM. • https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-eck-2-8-security-update/343854 https://www.elastic.co/community/security • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
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: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-2023-46666 – Elastic Sharepoint Online Python Connector Improper Access Control
https://notcve.org/view.php?id=CVE-2023-46666
An issue was discovered when using Document Level Security and the SPO "Limited Access" functionality in Elastic Sharepoint Online Python Connector. If a user is assigned limited access permissions to an item on a Sharepoint site then that user would have read permissions to all content on the Sharepoint site through Elasticsearch. Se descubrió un problema al utilizar la seguridad a nivel de documento y la funcionalidad de "acceso limitado" de SPO en Elastic Sharepoint Online Python Connector. Si a un usuario se le asignan permisos de acceso limitado a un elemento en un sitio de Sharepoint, ese usuario tendría permisos de lectura para todo el contenido del sitio de Sharepoint a través de Elasticsearch. • https://discuss.elastic.co/t/elastic-sharepoint-online-python-connector-v8-10-3-0-security-update/344732 https://www.elastic.co/community/security • CWE-284: Improper Access Control •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2023-31421 – Beats, Elastic Agent, APM Server, and Fleet Server Improper Certificate Validation issue
https://notcve.org/view.php?id=CVE-2023-31421
It was discovered that when acting as TLS clients, Beats, Elastic Agent, APM Server, and Fleet Server did not verify whether the server certificate is valid for the target IP address; however, certificate signature validation is still performed. More specifically, when the client is configured to connect to an IP address (instead of a hostname) it does not validate the server certificate's IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected. Se descubrió que cuando actuaban como Clientes TLS, Beats, Elastic Agent, APM Server y Fleet Server no verificaban si el certificado del servidor es válido para la dirección IP de destino; sin embargo, aún se realiza la validación de la firma del certificado. Más específicamente, cuando el cliente está configurado para conectarse a una dirección IP (en lugar de un nombre de host), no valida los valores IP SAN del certificado del servidor con esa dirección IP y la validación del certificado falla y, por lo tanto, la conexión no se bloquea como se esperaba. • https://discuss.elastic.co/t/beats-elastic-agent-apm-server-and-fleet-server-8-10-1-security-update-improper-certificate-validation-issue-esa-2023-16/343385 https://www.elastic.co/community/security • CWE-295: Improper Certificate Validation •