UBUNTU-CVE-2024-55553: High severity ubuntu/frr vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/frrto a version that resolves this vulnerability.Fixed in 7.2.1-1ubuntu0.2+esm5 - Upgrade
Upgrade
ubuntu/frrto a version that resolves this vulnerability.Fixed in 8.1-1ubuntu1.17 - Upgrade
Upgrade
ubuntu/frrto a version that resolves this vulnerability.Fixed in 8.4.4-1.1ubuntu6.8 - Upgrade
Upgrade
FRRouting (FRR)to a version that resolves this vulnerability.Fixed in 10.0.3 - Upgrade
Upgrade
FRRouting (FRR)to a version that resolves this vulnerability.Fixed in 10.1.2 - Upgrade
Upgrade
FRRouting (FRR)to a version that resolves this vulnerability.Fixed in 10.2.1 - Upgrade
Upgrade
FRRouting (FRR)to a version that resolves this vulnerability.Fixed in 10.3
Event History
Frequently Asked Questions
Which FRR deployments are exposed?
FRR versions from 6.0 through versions before the listed fixes are affected when they use RTR for RPKI route validation. The issue can affect FRR routers globally that use RPKI, particularly those carrying large full routing tables.
Is a non-default socket-buffer configuration required for the issue to occur?
No. The relevant internal socket buffer is typically 4 KB by default on most operating systems, and an RTR update whose total size exceeds that buffer triggers route re-validation. The condition can also occur organically during normal update activity.
What must occur to cause sustained impact?
An attacker can cause excessive RTR updates during an update interval, usually 30 minutes, to trigger RIB re-parsing and re-validation. Continuous issuance and withdrawal of large numbers of ROAs can keep validation running continuously.
What is the operational effect of exploitation?
Repeated full-table re-validation can degrade route-handling performance, especially where validating a large full table takes more than 30 minutes. It also increases BMP traffic sent to ingestors.
Which versions contain fixes?
Fixed versions are 10.0.3, 10.1.2, 10.2.1, and 10.3 or later.