Daemon crash via undersized labeled-unicast NLRI
Published Nov 6, 2023 · Updated Nov 4, 2025
Out-of-bounds read in FRRouting before 8.5 allows remote attackers to crash bgpd via a malformed labeled-unicast BGP update. bgp_nlri_get_labels accepts a label field shorter than three bytes, while the parser also advances past an absent Add-Path identifier before reading. A reachable, established BGP peer that sends the malformed NLRI can interrupt routing until the daemon recovers or restarts.
Summary
What happened
Out-of-bounds read in FRRouting before 8.5 allows remote attackers to crash bgpd via a malformed labeled-unicast BGP update. bgp_nlri_get_labels accepts a label field shorter than three bytes, while the parser also advances past an absent Add-Path identifier before reading. A reachable, established BGP peer that sends the malformed NLRI can interrupt routing until the daemon recovers or restarts.
The record
- CVE
- CVE-2023-38407
- Published
- Nov 6, 2023
- Updated
- Nov 4, 2025
- Vendor
- FRRouting
- Product
- FRRouting
- Classifications
- T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 6, 2023CVE 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=0 <8.5
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