FRRouting 4.0
Approved changes feed: RSS · Atom
cpe:2.3:a:frrouting:frrouting:4.0:*:*:*:*:*:*:*
part: a version: 4.0 update: *
| Vendor | Frrouting (e294935e-b43b-5a5a-9647-a9586c51d310) |
|---|---|
| Product | Frrouting (6fc7156a-ba42-560e-a551-8a0d86d6a1dc) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/frrouting/frr |
purl2cpe | 2026-06-01 10:16:02.342128 |
pkg:github/frrouting/frr |
purl2cpe | 2026-06-01 10:16:02.342130 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-5892 |
vulnerable | 2026-06-08 05:14:08.209899 |
Details available
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.
Published: 2019-01-10T17:00:00.000Z
Updated: 2024-08-04T20:09:23.750Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.