diff options
author | Zhang Peng <peng.zhang1.cn@windriver.com> | 2025-04-22 18:21:07 +0800 |
---|---|---|
committer | Armin Kuster <akuster808@gmail.com> | 2025-05-25 14:48:44 -0400 |
commit | 85275437cd64196d1bef8e16656df04201296fbf (patch) | |
tree | 211d15187cacbfdb43f667669bc982d290936563 /meta-python/recipes-devtools/python/python3-twisted/CVE-2024-41671-0002.patch | |
parent | 4c87bd7b937a0ab585352a3f3fb193d693106ed7 (diff) | |
download | meta-openembedded-85275437cd64196d1bef8e16656df04201296fbf.tar.gz |
frr: fix CVE-2024-55553
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.
Reference: [https://nvd.nist.gov/vuln/detail/CVE-2024-55553]
[https://frrouting.org/security/cve-2024-55553/]
Upstream patch: backport [https://github.com/FRRouting/frr/commit/b0800bfdf04b4fcf48504737ebfe4ba7f05268d3]
Signed-off-by: Zhang Peng <peng.zhang1.cn@windriver.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-twisted/CVE-2024-41671-0002.patch')
0 files changed, 0 insertions, 0 deletions