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. Affected Versions: FRRouting <6.0. Fixed Versions: 10.0.3, 10.1.2, 10.2.1, >= 10.3.
Metrics
Affected Vendors & Products
References
History
Thu, 09 Jan 2025 22:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In FRRouting (FRR) before 10.3, it is possible for an attacker to trigger repeated RIB revalidation by sending approximately 500 RPKI updates, potentially leading to prolonged revalidation times and a Denial of Service (DoS) scenario. | 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. Affected Versions: FRRouting <6.0. Fixed Versions: 10.0.3, 10.1.2, 10.2.1, >= 10.3. |
Thu, 09 Jan 2025 14:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Title | frr: DoS via repeated RIB revalidation | |
Weaknesses | CWE-400 | |
References |
| |
Metrics |
threat_severity
|
threat_severity
|
Tue, 07 Jan 2025 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-404 | |
Metrics |
cvssV3_1
|
Mon, 06 Jan 2025 22:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In FRRouting (FRR) before 10.3, it is possible for an attacker to trigger repeated RIB revalidation by sending approximately 500 RPKI updates, potentially leading to prolonged revalidation times and a Denial of Service (DoS) scenario. | |
References |
|
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2025-01-06T00:00:00
Updated: 2025-01-09T21:57:55.632985Z
Reserved: 2024-12-08T00:00:00
Link: CVE-2024-55553
Vulnrichment
Updated: 2025-01-07T14:59:01.660Z
NVD
Status : Received
Published: 2025-01-06T23:15:07.637
Modified: 2025-01-09T22:15:29.350
Link: CVE-2024-55553
Redhat