[SECURITY] [DLA 4029-1] frr security update
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
From: Arturo Borrero Gonzalez <arturo@debian.org>
To: debian-lts-announce@lists.debian.org
Subject: [SECURITY] [DLA 4029-1] frr security update
- -------------------------------------------------------------------------
Debian LTS Advisory DLA-4029-1 debian-lts@lists.debian.org
https://www.debian.org/lts/security/ Arturo Borrero Gonzalez
January 23, 2025 https://wiki.debian.org/LTS
- -------------------------------------------------------------------------
Package : frr
Version : 7.5.1-1.1+deb11u4
CVE ID : CVE-2024-55553
In FRR, the internet routing protocol suite software, 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.
For Debian 11 bullseye, this problem has been fixed in version
7.5.1-1.1+deb11u4.
We recommend that you upgrade your frr packages.
For the detailed security status of frr please refer to
its security tracker page at:
https://security-tracker.debian.org/tracker/frr
Further information about Debian LTS security advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://wiki.debian.org/LTS
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAmeSMLIACgkQaOcTmB0V
Ffi7FQ/9HTlZWe/qCh6ART+W1ly4Cy9JsTzJ+xdf2Q6JXuDZd4QnjZI8Qu/RkQGy
+rpH+JLzU8KZm4+X3X5dGdGo0SlRkxBXfIvfdcRXdEQ4oz5YGnX4RVX4pwpD8/0Y
GEGn/4rM4MP2qXMKoZFpCa2878rYFEFSE9j8Je8CmekBySK0HbD+V4y0fWeoqi5M
IJI/JtyQHhzYXLTun2/BePvxs51mVJlnLlWjDpPWYsCRNVNbKZ/68cxUr9QL9Mcd
z+qTsEgbw+1nM6JnjYbwhW6M1V7TV4w2dhZww1Hx3tCHJdFmCFAHc/c8VnOEi7T4
MBsZHb+kAJOPAkXYDSWq2OTMlANvS5sW9iCW1F+0Zyk0jYvOD32A4o8m7GMm1E7K
I6xNeYUgm4+8Ob6hxWOgWBMNaIJXviFRDY6o67MCngEbbCaEG3C4Pg5qZwJ0HBtP
fghq2WqRSLeTEzyN2sNxZ0116KuGWiUM7Qjq8WUiRXT2zgHLII2GRu/2p2Gqi81y
1w8BZpFST23Ci3mysEdYy7Br7Q3x0YOjYiXUpK3aYHmw8ie7eWXlNnMhcDN4Y4t8
iN+2CCgMTx+FAUrebNRA0eNp7FsNiN1lVSeiz6TcMVtoRNo+UsbXIill616Lqdvm
u/Kpm7OCOKHsPPJKme8IRXr6AFn905IsLdvKeLvhCU2+gpfP/m0=
=ueO2
-----END PGP SIGNATURE-----
Reply to: