Process crash via truncated RTR message
Published Apr 21, 2025 · Updated Apr 21, 2025
Off-by-one error in GoBGP before 3.35.0 allows remote attackers to crash the process by sending a truncated RTR message. In pkg/packet/rtr/rtr.go, ParseRTR accepts an undersized byte slice and indexes its second byte without first establishing that the byte exists. Reachability requires an enabled RPKI cache connection, and malformed RTR input can panic the parser and interrupt routing service.
Summary
What happened
Off-by-one error in GoBGP before 3.35.0 allows remote attackers to crash the process by sending a truncated RTR message. In pkg/packet/rtr/rtr.go, ParseRTR accepts an undersized byte slice and indexes its second byte without first establishing that the byte exists. Reachability requires an enabled RPKI cache connection, and malformed RTR input can panic the parser and interrupt routing service.
The record
- CVE
- CVE-2025-43973
- Published
- Apr 21, 2025
- Updated
- Apr 21, 2025
- Vendor
- GoBGP
- Product
- GoBGP
- Classifications
- CWE-193, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2025CVE publishedPublication date reported by the CVE source.
- Apr 21, 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 <3.35.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.
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