CVE-2022-26129: Buffer Overflow
Published Mar 3, 2022
·Updated
Buffer overflow vulnerabilities exist in FRRouting through 8.1.0 due to wrong checks on the subtlv length in the functions, parsehellosubtlv, parseihusubtlv, and parseupdatesubtlv in babeld/message.c.
Affected Software
2 affected componentsFixes available
Frrouting FRRouting<=8.1
debian/frr<=7.5.1-1.1+deb11u2
7.5.1-1.1+deb11u48.4.4-1.1~deb12u110.2.1-2
Remediation
Event History
Mar 3, 2022
CVE Published
via MITRE·05:24 PM
Data Sourced
via MITRE·05:24 PM
DescriptionWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Jun 5, 2024
Data Sourced
via Launchpad·05:52 PM
Description
Sep 13, 2024
Data Sourced
via Ubuntu·06:07 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is CVE-2022-26129?
CVE-2022-26129 is a vulnerability that exists in FRRouting through version 8.1.0.
2
What is the severity of CVE-2022-26129?
CVE-2022-26129 has a severity score of 7.8 (high).
3
How does CVE-2022-26129 affect FRRouting?
CVE-2022-26129 causes buffer overflow vulnerabilities due to incorrect checks on the subtlv length in certain functions in babeld/message.c.
4
Which versions of FRRouting are affected by CVE-2022-26129?
FRRouting versions up to and including 8.1.0 are affected by CVE-2022-26129.
5
How can I fix CVE-2022-26129 in FRRouting?
To fix CVE-2022-26129 in FRRouting, you should update to version 8.4.4-1.1 or later. If you are using the Debian package, update to version 6.0.2-2+deb10u1, 7.5.1-1.1+deb10u1, or 7.5.1-1.1+deb11u2.