You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
NIST has updated the
NVD program announcement page with additional information regarding
recent concerns and the temporary delays in enrichment efforts.
CVE-2019-5892
Detail
Description
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.
NVD Analysts use publicly available information to associate vector strings and CVSS scores. We also display any CVSS information provided within the CVE List from the CNA.
Note: NVD Analysts have published a CVSS score for this CVE based on publicly available information at the time of analysis. The CNA has not provided a score within the CVE List.
NVD Analysts use publicly available information to associate vector strings and CVSS scores. We also display any CVSS information provided within the CVE List from the CNA.
Note: NVD Analysts have published a CVSS score for this CVE based on publicly available information at the time of analysis. The CNA has not provided a score within the CVE List.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to nvd@nist.gov.
OR
*cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* versions from (including) 2.0 up to (including) 2.0.2
*cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* versions from (including) 3.0 up to (excluding) 3.0.4
*cpe:2.3:a:frrouting:frrouting:4.0:*:*:*:*:*:*:*
*cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.0.2
*cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* versions from (including) 6.0 up to (excluding) 6.0.2
Added
CVSS V2
(AV:N/AC:L/Au:S/C:N/I:N/A:P)
Added
CVSS V3
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Added
CWE
CWE-20
Changed
Reference Type
https://frrouting.org/community/security/cve-2019-5892.html No Types Assigned
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, as used in Cumulus Linux through 3.7.x and other products, 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
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
Quick Info
CVE Dictionary Entry: CVE-2019-5892 NVD
Published Date: 01/10/2019 NVD
Last Modified: 08/24/2020
Source: MITRE