← volver
CVE-2022-20943

CVE-2022-20943

CVSS 5.8 MEDIUMEPSS 0.9%CWE-244
En resumen

Un fallo en la herramienta de seguridad Snort de Cisco permite que atacantes envíen mensajes de red especiales (SMB2) que pueden derribar el sistema de seguridad o eludir sus protecciones, permitiendo que tráfico malicioso llegue a redes protegidas.

Detalle técnico

La vulnerabilidad existe en la gestión inadecuada de recursos dentro del procesador SMB2 de Snort 3 al manejar tráfico SMB2 de alta velocidad. Un atacante remoto no autenticado puede provocar recargas del proceso Snort causando DoS; cuando preserve-connection está habilitado (por defecto), la elusión de políticas y entrega de carga se hacen posibles sin autenticación ni acceso previo.

Resumen generado y traducido por IA a partir de la descripción oficial.
Multiple vulnerabilities in the Server Message Block Version 2 (SMB2) processor of the Snort detection engine on multiple Cisco products could allow an unauthenticated, remote attacker to bypass the configured policies or cause a denial of service (DoS) condition on an affected device. These vulnerabilities are due to improper management of system resources when the Snort detection engine is processing SMB2 traffic. An attacker could exploit these vulnerabilities by sending a high rate of certain types of SMB2 packets through an affected device. A successful exploit could allow the attacker to trigger a reload of the Snort process, resulting in a DoS condition. Note: When the snort preserve-connection option is enabled for the Snort detection engine, a successful exploit could also allow the attacker to bypass the configured policies and deliver a malicious payload to the protected network. The snort preserve-connection setting is enabled by default. See the Details ["#details"] section of this advisory for more information. Note: Only products that have Snort 3 configured are affected. Products that are configured with Snort 2 are not affected.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L

¿Quieres saber si tu infraestructura está expuesta a esto?

Hablar con TrueHacking →