bgpd in FRRouting FRR (aka Free Range Routing) 2.x and 3.x before 3.0.4, 4.x before 4.0.1, 5.x before 5.0.2, and 6.x before 6.0.2 (not affecting Cumulus Linux or VyOS), when ENABLE_BGP_VNC is used for Virtual Network Control, allows remote attackers to cause a denial of service (peering session flap) via attribute 255 in a BGP UPDATE packet. This occurred during Disco in January 2019 because FRR does not implement RFC 7606, and therefore the packets with 255 were considered invalid VNC data and the BGP session was closed.
References
Link | Resource |
---|---|
https://frrouting.org/community/security/cve-2019-5892.html | Vendor Advisory |
https://github.com/FRRouting/frr/commit/943d595a018e69b550db08cccba1d0778a86705a | Patch Third Party Advisory |
https://github.com/FRRouting/frr/releases/tag/frr-3.0.4 | Release Notes Third Party Advisory |
https://github.com/FRRouting/frr/releases/tag/frr-4.0.1 | Release Notes Third Party Advisory |
https://github.com/FRRouting/frr/releases/tag/frr-5.0.2 | Release Notes Third Party Advisory |
https://github.com/FRRouting/frr/releases/tag/frr-6.0.2 | Release Notes Third Party Advisory |
https://lists.frrouting.org/pipermail/frog/2019-January/000404.html | Patch Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2019-01-10 17:29
Updated : 2020-08-24 17:37
NVD link : CVE-2019-5892
Mitre link : CVE-2019-5892
CVE.ORG link : CVE-2019-5892
JSON object : View
Products Affected
frrouting
- frrouting
CWE
CWE-436
Interpretation Conflict