The OSPF version 3 (OSPFv3) feature of Cisco NX-OS Software vulnerability could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.
This vulnerability is due to incomplete input validation of specific OSPFv3 packets. An attacker could exploit this vulnerability by sending a malicious OSPFv3 link-state advertisement (LSA) to an affected device. A successful exploit could allow the attacker to cause the OSPFv3 process to crash and restart multiple times, causing the affected device to reload and resulting in a DoS condition.
The OSPFv3 feature is disabled by default. To exploit this vulnerability, an attacker must be able to establish a full OSPFv3 neighbor state with an affected device.
Cisco released software updates that address this vulnerability, according to the 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 are configured for OSPFv3 routing on at least one interface:
- Nexus 3000 Series Switches (CSCvz68748)
- Nexus 5500 Platform Switches (CSCwb50015)
- Nexus 5600 Platform Switches (CSCwb50015)
- Nexus 6000 Series Switches (CSCwb50015)
- Nexus 7000 Series Switches (CSCwb50013)
- Nexus 9000 Series Fabric Switches in ACI mode (CSCwb50012)
- Nexus 9000 Series Switches in standalone NX-OS mode (CSCvz68748)
The OSPFv3 implementation on Cisco NX-OS Software only supports the transport of IPv6 routing information and requires an IPv6 address to be configured on any interface enabled for OSPFv3 routing.
To exploit this vulnerability, an attacker must be able to establish a full OSPFv3 neighbor state with an affected device. This requires the attacker to use OSPFv3 parameters compatible with the affected device, including valid authentication information if OSPFv3 authentication is configured on the device.
A device running OSPFv3 may communicate with a neighbor one or more Layer 3 hops away only if a virtual link to such neighbor is explicitly configured on the device. If no OSPFv3 virtual link is configured, an attacker must be Layer 2 adjacent to the affected device to exploit this vulnerability.
As mentioned, there are no workarounds that address this vulnerability. However, OSPFv3 authentication can be used to reduce the attack surface by allowing only authenticated peers to establish a full OSPFv3 neighbor state. OSPFv3 authentication is supported on Nexus 3000 and Nexus 7000 Series Switches and on Nexus 9000 Series Switches in standalone NX-OS mode. It is not currently supported on Nexus 5500 and Nexus 5600 Platform Switches, Nexus 6000 Series Switches and Nexus 9000 Series Fabric Switches in ACI mode.
Meanwhile, Cisco also fixed a vulnerability in its Discovery Protocol feature of Cisco FXOS Software and Cisco NX-OS Software that could allow an unauthenticated, adjacent attacker to execute arbitrary code with root privileges or cause a denial of service (DoS) condition on an affected device.
This vulnerability is due to improper input validation of specific values that are within a Cisco Discovery Protocol message. An attacker could exploit this vulnerability by sending a malicious Cisco Discovery Protocol packet to an affected device. A successful exploit could allow the attacker to execute arbitrary code with root privileges or cause the Cisco Discovery Protocol process to crash and restart multiple times, which would cause the affected device to reload, resulting in a DoS condition.
Cisco Discovery Protocol is a Layer 2 protocol. To exploit this vulnerability, an attacker must be in the same broadcast domain as the affected device.
Cisco released software updates that address this vulnerability, according to the 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 FXOS or NX-OS Software and have Cisco Discovery Protocol enabled both globally and on at least one interface:
- Firepower 4100 Series (CSCwb74498)
- Firepower 9300 Security Appliances (CSCwb74498)
- MDS 9000 Series Multilayer Switches (CSCwb74494)
- Nexus 1000 Virtual Edge for VMware vSphere (CSCwb74495)
- Nexus 1000V Switch for Microsoft Hyper-V (CSCwb74495)
- Nexus 1000V Switch for VMware vSphere (CSCwb74495)
- Nexus 3000 Series Switches (CSCwb70210)
- Nexus 5500 Platform Switches (CSCwb74496)
- Nexus 5600 Platform Switches (CSCwb74496)
- Nexus 6000 Series Switches (CSCwb74496)
- Nexus 7000 Series Switches (CSCwb74494)
- Nexus 9000 Series Fabric Switches in ACI mode (CSCwb74493)
- Nexus 9000 Series Switches in standalone NX-OS mode (CSCwb70210)
- UCS 6200 Series Fabric Interconnects (CSCwb74497)
- UCS 6300 Series Fabric Interconnects (CSCwb74497)
- UCS 6400 Series Fabric Interconnects (CSCwb74513)
Cisco Discovery Protocol is enabled by default on all of the products in the preceding list except Cisco Nexus 9000 Series Fabric Switches in ACI mode.
As mentioned, there are no workarounds that address this vulnerability. However, users who do not use Cisco Discovery Protocol can disable the feature either globally, to fully close the attack vector, or on individual interfaces, to reduce the attack surface.
Click here for additional information on other vulnerability fixes by Cisco.

