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.
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 Frrouting | <=8.4 | |
Debian Debian Linux | =10.0 | |
Debian Debian Linux | =11.0 | |
Debian Debian Linux | =12.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-40302 is a vulnerability discovered in bgpd in FRRouting (FRR) through 8.4, which allows attackers to cause a denial of service due to an assertion failure and daemon restart, or an out-of-bounds read, by crafting a BGP OPEN message with an option of type 0xff (Extended Length).
CVE-2022-40302 affects FRRouting versions up to and including 8.4.
The severity of CVE-2022-40302 is medium, with a CVSSv3 score of 6.5.
To fix CVE-2022-40302, it is recommended to upgrade FRRouting to version 8.4.2 or later.
Yes, you can find references for CVE-2022-40302 at the following links: [GitHub Releases](https://github.com/FRRouting/frr/releases), [GitHub Issue #13427](https://github.com/FRRouting/frr/issues/13427), [GitHub Issue #13480](https://github.com/FRRouting/frr/issues/13480).