CVE-2024-55553

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.

Published: 2025-01-06 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-55553 is rated Moderate Risk (45/100): CVSS High severity, with low exploitation likelihood (EPSS 0.21%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-55553

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-15 0.42% 0.21% -0.21%
2 2026-02-14 0.47% 0.42% -0.05%
3 2025-11-02 0.47%

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-55553

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-55553

OS Trackers for CVE-2024-55553

vendor priority summary link
debian not yet assigned CVE-2024-55553 not yet assigned priority: Debian including 1 source packages (frr), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-55553
redhat high https://access.redhat.com/security/cve/CVE-2024-55553
suse medium CVE-2024-55553 severity moderate: SUSE including 64 source package names (frr-10.2.1-1.1, frr-10.2.1-150700.1.7, …), 245 product×package rows across 35 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (35 product lines)): Known Not Affected 177, Fixed 68. https://www.suse.com/security/cve/CVE-2024-55553/
ubuntu medium CVE-2024-55553 medium priority: Ubuntu including 2 source packages (frr, quagga), 14 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, upstream, xenial): released 5, DNE 4, not-affected 4, ignored 1. https://ubuntu.com/security/CVE-2024-55553

Affected software / configurations for CVE-2024-55553

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-55553

cvelogic Threat Intelligence