CVE-2018-14633

A security flaw was found in the chap_server_compute_md5() function in the ISCSI target code in the Linux kernel in a way an authentication request from an ISCSI initiator is processed. An unauthenticated remote attacker can cause a stack buffer overflow and smash up to 17 bytes of the stack. The attack requires the iSCSI target to be enabled on the victim host. Depending on how the target's code was built (i.e. depending on a compiler, compile flags and hardware architecture) an attack may lead to a system crash and thus to a denial-of-service or possibly to a non-authorized access to data exported by an iSCSI target. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is highly unlikely. Kernel versions 4.18.x, 4.14.x and 3.10.x are believed to be vulnerable.

A security flaw was found in the chap_server_compute_md5() function in the ISCSI target code in the Linux kernel in a way an authentication request from an ISCSI initiator is processed. An unauthenticated remote attacker can cause a stack buffer overflow and smash up to 17 bytes of the stack. The attack requires the iSCSI target to be enabled on the victim host. Depending on how the target's code was built (i.e. depending on a compiler, compile flags and hardware architecture) an attack may lead to a system crash and thus to a denial-of-service or possibly to a non-authorized access to data exported by an iSCSI target. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is highly unlikely. Kernel versions 4.18.x, 4.14.x and 3.10.x are believed to be vulnerable.

Se ha detectado un error de seguridad en la función chap_server_compute_md5() en el código ISCSI objetivo en el kernel de Linux, por la forma en la que se procesa una petición de autenticación de un iniciador ISCSI. Un atacante remoto no autenticado puede provocar un desbordamiento de búfer basado en pila y quebrar hasta 17 bytes de la pila. El ataque requiere que el iSCSI objetivo esté habilitado en el host de la víctima. Dependiendo de cómo se haya construido el código del objetivo (dependiendo de un compilador, marcas de compilación o arquitectura del hardware), un ataque podría conducir a un cierre inesperado del sistema y, por lo tanto, a una denegación de servicio (DoS) o, posiblemente, a un acceso no autorizado a los datos exportados por un objetivo iSCSI. Debido a la naturaleza del error, no se puede descartar totalmente un escalado de privilegios, aunque se cree que es altamente improbable. Se cree que las versiones 4.18.x, 4.14.x y 3.10.x del kernel se han visto afectadas.