First published: Wed May 03 2023(Updated: )
An issue was discovered in bgpd in FRRouting (FRR) through 8.4. By crafting a BGP OPEN message with an option of type 0xff (Extended Length from RFC 9072), attackers may cause a denial of service (assertion failure and daemon restart, or out-of-bounds read). This is possible because of inconsistent boundary checks that do not account for reading 3 bytes (instead of 2) in this 0xff case. NOTE: this behavior occurs in bgp_open_option_parse in the bgp_open.c file, a different location (with a different attack vector) relative to CVE-2022-40302.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/frr | <=6.0.2-2+deb10u1 | 7.5.1-1.1+deb10u1 7.5.1-1.1+deb11u2 8.4.4-1.1~deb12u1 8.4.4-1.1 |
Frrouting bgpd | <=8.4 | |
Debian | =10.0 | |
Debian | =11.0 | |
Debian | =12.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2022-40318 is medium.
CVE-2022-40318 affects FRRouting through version 8.4.
CVE-2022-40318 can cause a denial of service by triggering an assertion failure and daemon restart or out-of-bounds read.
To fix CVE-2022-40318 in FRRouting, you should update to the latest version available.
You can find more information about CVE-2022-40318 on the GitHub releases and issues pages for FRRouting.