FRRouting up to 6.0.1 bgpd BGP UPDATE Packet input validation

Summaryinfo

A vulnerability was found in FRRouting up to 2.x/3.0.3/4.0.0/5.0.1/6.0.1. It has been classified as problematic. Affected is an unknown function of the component bgpd. The manipulation as part of BGP UPDATE Packet leads to input validation. This vulnerability is traded as CVE-2019-5892. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in FRRouting up to 2.x/3.0.3/4.0.0/5.0.1/6.0.1 and classified as problematic. This issue affects an unknown code block of the component bgpd. The manipulation as part of a BGP UPDATE Packet leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is availability. The summary by CVE is:

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.

The bug was discovered 01/10/2019. The weakness was shared 01/10/2019 (Website). The advisory is shared at frrouting.org. The identification of this vulnerability is CVE-2019-5892 since 01/10/2019. The attack may be initiated remotely. The requirement for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available.

Upgrading to version 3.0.4, 4.0.1, 5.0.2 or 6.0.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• FRRouting

Version

• 2.x
• 3.0.0
• 3.0.1
• 3.0.2
• 3.0.3
• 4.0
• 5.0.0
• 5.0.1
• 6.0.0
• 6.0.1

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion