CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 1CVE-2022-26125 – frrouting: overflow bugs in unpack_tlv_router_cap
https://notcve.org/view.php?id=CVE-2022-26125
Buffer overflow vulnerabilities exist in FRRouting through 8.1.0 due to wrong checks on the input packet length in isisd/isis_tlvs.c. Se presentan vulnerabilidades de desbordamiento del búfer en FRRouting versiones hasta 8.1.0, debido a comprobaciones erróneas de la longitud del paquete de entrada en el archivo isisd/isis_tlvs.c frrouting is vulnerable to a flaw that can cause buffer overflow through due to incorrect checks on the input packet length when processing type-length-value packets. There is high impact to availability due to the fact that the process up-time can be made unreliable. • https://github.com/FRRouting/frr/issues/10507 https://lists.debian.org/debian-lts-announce/2024/04/msg00019.html https://access.redhat.com/security/cve/CVE-2022-26125 https://bugzilla.redhat.com/show_bug.cgi?id=2058628 • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer CWE-1284: Improper Validation of Specified Quantity in Input •
CVSS: 6.5EPSS: 1%CPEs: 5EXPL: 0CVE-2019-5892
https://notcve.org/view.php?id=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 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ó. • https://frrouting.org/community/security/cve-2019-5892.html https://github.com/FRRouting/frr/commit/943d595a018e69b550db08cccba1d0778a86705a https://github.com/FRRouting/frr/releases/tag/frr-3.0.4 https://github.com/FRRouting/frr/releases/tag/frr-4.0.1 https://github.com/FRRouting/frr/releases/tag/frr-5.0.2 https://github.com/FRRouting/frr/releases/tag/frr-6.0.2 https://lists.frrouting.org/pipermail/frog/2019-January/000404.html • CWE-436: Interpretation Conflict •