CVE-2024-55553: High severity Frrouting FRR vulnerability
In FRRouting (FRR) all routes are re-validated if the total size of an update received via RTR exceeds the internal socket's buffer size
Other sources
In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal socket's buffer size, default 4K on most OSes. An attacker can use this to trigger re-parsing of the RIB for FRR routers using RTR by causing more than this number of updates during an update interval (usually 30 minutes). Additionally, this effect regularly occurs organically. Furthermore, an attacker can use this to trigger route validation continuously. Given that routers with large full tables may need more than 30 minutes to fully re-validate the table, continuous issuance/withdrawal of large numbers of ROA may be used to impact the route handling performance of all FRR instances using RPKI globally. Additionally, the re-validation will cause heightened BMP traffic to ingestors. Fixed Versions: 10.0.3, 10.1.2, 10.2.1, >= 10.3.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-55553?
CVE-2024-55553 has been rated as a medium-severity vulnerability due to its potential to disrupt routing operations.
How do I fix CVE-2024-55553?
To fix CVE-2024-55553, update to FRRouting version 10.3 or later, as well as ensure that you have the latest security patches for your installed version.
What systems are affected by CVE-2024-55553?
CVE-2024-55553 affects all versions of FRRouting from 6.0 up to but not including 10.3.
Can CVE-2024-55553 be exploited remotely?
Yes, an attacker can exploit CVE-2024-55553 remotely by sending specially crafted updates via the RTR protocol.
What are the potential consequences of exploiting CVE-2024-55553?
Exploiting CVE-2024-55553 may lead to routing information base (RIB) corruption, causing network disruptions and misrouting of traffic.