Babel daemon crash via unchecked packet body length
Published Mar 3, 2022 · Updated Nov 4, 2025
Heap buffer overflow in FRRouting 8.1.0 and earlier allows remote attackers to crash babeld with a truncated Babel packet. babel_packet_examin trusts the body length declared in the packet header and iterates past the received packet buffer without checking that bodylen plus four bytes fits packetlen. The Babel daemon must be enabled and Babel routing configured on an attacker-reachable interface; the public report demonstrates an out-of-bounds read rather than code execution.
Summary
What happened
Heap buffer overflow in FRRouting 8.1.0 and earlier allows remote attackers to crash babeld with a truncated Babel packet. babel_packet_examin trusts the body length declared in the packet header and iterates past the received packet buffer without checking that bodylen plus four bytes fits packetlen. The Babel daemon must be enabled and Babel routing configured on an attacker-reachable interface; the public report demonstrates an out-of-bounds read rather than code execution.
The record
- CVE
- CVE-2022-26127
- Published
- Mar 3, 2022
- Updated
- Nov 4, 2025
- Vendor
- FRRouting
- Product
- FRRouting
- Classifications
- CWE-119, CWE-1284, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2022CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=through 8.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo