On affected platforms running Arista EOS with BGP configured, a specially crafted packet can cause the BGP agent to crash.
Successful exploitation causes the BGP agent process to terminate, resulting in the loss of all BGP sessions on the affected device and possible disruption to network routing until the process recovers. Due to the nature of the vulnerability, it may also be possible for a sophisticated attacker to achieve arbitrary code execution, which could compromise the confidentiality and integrity of the affected system.
switch>show ip bgp summary
BGP summary information for VRF default
Router identifier 10.0.0.1, local AS number 65000
Neighbor Status Codes: m - Under maintenance
Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc
10.0.0.2 4 65001 100 100 0 0 01:00:00 Estab 10 10
switch>show running-config all | inc service routing protocols
service routing protocols model multi-agent
For BGP sessions that do not rely on the Tunnel Encapsulation Attribute, a workaround is to remove all received Tunnel Encapsulation Attributes by configuring attribute discard, for example:
neighbor default received attribute discard 23
Alternatively, a recommended mitigation to reduce exposure to this vulnerability is to configure BGP peer authentication using TCP-AO in order to ensure that only authorized peers can establish a BGP session.