In one vulnerability, there is an issue in the External Border Gateway Protocol (eBGP) implementation of Cisco NX-OS Software that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.
This vulnerability exists because the mapping to eBGP traffic goes to a shared hardware rate-limiter queue. An attacker could exploit this vulnerability by sending large amounts of network traffic with certain characteristics through an affected device. A successful exploit could allow the attacker to cause eBGP neighbor sessions to end up dropped, leading to a DoS condition in the network.
Cisco released software updates that address this vulnerability, according to an advisory. There are no workarounds that address this vulnerability.
This vulnerability affects Cisco Nexus 3600 Series Switches and Cisco Nexus 9500 R-Series Line Cards if they are running a vulnerable release of Cisco NX-OS Software, they have BGP functionality with at least one BGP neighbor (peer) configured with a different Autonomous System (AS) value, and they have one of the following Cisco product IDs:
- N3K-C36180YC-R
- N3K-C3636C-R
- N9K-X9624D-R2
- N9K-X9636C-R
- N9K-X9636C-RX
- N9K-X9636Q-R
- N9K-X96136YC-R
The list of affected Cisco Nexus 3600 Series Switch product IDs and Cisco Nexus 9500 R-Series Line Card product IDs was accurate at the time of publication. For specific questions about a product ID, contact the Cisco Technical Assistance Center (TAC).
To determine the configuration of Cisco Nexus device and if the BGP feature and an eBGP neighbor is active, use the show running-config | include “router bgp” and show running-config | include “neighbor” = commands from the Cisco NX-OS Software CLI and verify the feature is enabled.
The following example shows the BGP feature enabled with one eBGP neighbor on a device that is running Cisco NX-OS Software:
nxos-switch# show running-config | include “router bgp”
router bgp 1
nxos-switch# show running-config | include “neighbor”
neighbor 10.10.10.2 remote-as 2
In another issue, there is a vulnerability with the handling of MPLS traffic for Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause the netstack process to unexpectedly restart, which could cause the device to stop processing network traffic or to reload.
This vulnerability is due to lack of proper error checking when processing an ingress MPLS frame. An attacker could exploit this vulnerability by sending a crafted IPv6 packet encapsulated within an MPLS frame to an MPLS-enabled interface of the targeted device. A successful exploit could allow the attacker to cause a denial of service (DoS) condition.
The IPv6 packet can end up generated multiple hops away from the targeted device and then encapsulated within MPLS. The DoS condition may occur when the NX-OS device processes the packet.
Cisco released software updates that address this vulnerability, according to an advisory. There are no workarounds that address this vulnerability.
This vulnerability affects the following Cisco products if they are running a vulnerable release of Cisco NX-OS Software and have MPLS configured:
- Nexus 3000 Series Switches (CSCwh42690)
- Nexus 5500 Platform Switches (CSCva52387)
- Nexus 5600 Platform Switches (CSCva52387)
- Nexus 6000 Series Switches (CSCva52387)
- Nexus 7000 Series Switches (CSCva52387)
- Nexus 9000 Series Switches in standalone NX-OS mode (CSCwh42690)
To determine whether a device is configured for MPLS, use the show mpls interface detail CLI command. If the switch is configured for MPLS and is configured to use MPLS on at least one interface, the output will include MPLS operational, as shown in the following example:
nxos# show mpls interface detail
Interface Ethernet1/4/1:
ldp enabled
MPLS operational
Label space id 0x10000001
MPLS sub-layer Ethernet1/4/1-mpls layer(0x26000001)
Interface Ethernet1/6/1:
ldp enabled
MPLS operational
Label space id 0x10000001
MPLS sub-layer Ethernet1/6/1-mpls layer(0x26000002)
If the show mpls interface detail is not a valid CLI command on the device, the device can be considered not vulnerable.
Click here for a listing of other Cisco vulnerability updates.

