CVE-2019-5892

bgpd in FRRouting FRR (aka Free Range Routing) 2.x and 3.x before 3.0.4, 4.x before 4.0.1, 5.x before 5.0.2, and 6.x before 6.0.2 (not affecting Cumulus Linux or VyOS), when ENABLE_BGP_VNC is used for Virtual Network Control, allows remote attackers to cause a denial of service (peering session flap) via attribute 255 in a BGP UPDATE packet. This occurred during Disco in January 2019 because FRR does not implement RFC 7606, and therefore the packets with 255 were considered invalid VNC data and the BGP session was closed.

bgpd in FRRouting FRR (aka Free Range Routing) 2.x and 3.x before 3.0.4, 4.x before 4.0.1, 5.x before 5.0.2, and 6.x before 6.0.2 (not affecting Cumulus Linux or VyOS), when ENABLE_BGP_VNC is used for Virtual Network Control, allows remote attackers to cause a denial of service (peering session flap) via attribute 255 in a BGP UPDATE packet. This occurred during Disco in January 2019 because FRR does not implement RFC 7606, and therefore the packets with 255 were considered invalid VNC data and the BGP session was closed.

bgpd en FRRouting FRR (también conocido como Free Range Routing), en versiones 2.x y 3.x anteriores a la 3.0.4, versiones 4.x anteriores a la 4.0.1, versiones 5.x anteriores a la 5.0.2 y versiones 6.x anteriores a la 6.0.2 (no afecta a Cumulus Linux o VyOS), cuando ENABLE_BGP_VNC se emplea para Virtual Network Control, permite que atacantes remotos provoquen una denegación de servicio (flap de la sesión de emparejamiento) mediante el atributo 255 en un paquete BGP UPDATE. Esto ocurrió durante Disco en enero de 2019 debido a que FRR no implementa RFC 7606 y, por lo tanto, los paquetes con 255 se consideraron datos VNC inválidos y la sesión BGP se cerró.