Unauthenticated bgpd crash via malformed BGP UPDATE
Published Nov 3, 2023 · Updated Nov 4, 2025
Improper BGP UPDATE handling in FRRouting FRR 9.0.1 and earlier allows remote attackers to crash bgpd via a crafted message. The bgp_update_receive path continued parsing trailing NLRI after MP_UNREACH_NLRI even when mandatory path attributes were absent. Any unauthenticated BGP peer able to send the malformed UPDATE can terminate the routing daemon, interrupting BGP service without disclosing or altering data.
Summary
What happened
Improper BGP UPDATE handling in FRRouting FRR 9.0.1 and earlier allows remote attackers to crash bgpd via a crafted message. The bgp_update_receive path continued parsing trailing NLRI after MP_UNREACH_NLRI even when mandatory path attributes were absent. Any unauthenticated BGP peer able to send the malformed UPDATE can terminate the routing daemon, interrupting BGP service without disclosing or altering data.
The record
- CVE
- CVE-2023-47234
- Published
- Nov 3, 2023
- Updated
- Nov 4, 2025
- Vendor
- FRRouting
- Product
- FRRouting
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 3, 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 <=9.0.1
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