CVE-2019-5892 json
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 affe…
published 7y ago modified 4mo ago also EUVD-2019-15461
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- frrouting frrouting 3.0.4, 5.0.2, 6.0.2
- github.com/FRRouting/frr@943d595 commit
- github.com/FRRouting/frr/releases/tag/frr-3.0.4 release
- github.com/FRRouting/frr/releases/tag/frr-5.0.2 release
- github.com/FRRouting/frr/releases/tag/frr-6.0.2 release
- github.com/FRRouting/frr/releases/tag/frr-4.0.1 release
- lists.frrouting.org/pipermail/frog/2019-January/000404.html advisory
Is CVE-2019-5892 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.72% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-436 Interpretation Conflict
References
-
github.com
/FRRouting/frr/commit/943d595a018e69b550db08cccba1d0778a86705a
patch, third-party-advisory
-
lists.frrouting.org
/pipermail/frog/2019-January/000404.html
patch, vendor-advisory
-
frrouting.org
/community/security/cve-2019-5892.html
vendor-advisory
-
github.com
/FRRouting/frr/releases/tag/frr-3.0.4
release-notes, third-party-advisory
-
github.com
/FRRouting/frr/releases/tag/frr-5.0.2
release-notes, third-party-advisory
-
github.com
/FRRouting/frr/releases/tag/frr-6.0.2
release-notes, third-party-advisory
-
github.com
/FRRouting/frr/releases/tag/frr-4.0.1
release-notes, third-party-advisory
Sources
- CVE List CVE-2019-5892
- NVD CVE-2019-5892
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.