Cisco has a fix for multiple products running its NX-OS Software support IP in IP packet encapsulation and decapsulation when a tunnel interface is manually configured on the device.
The device is not expected to decapsulate and process any IP in IP traffic not destined to such a tunnel interface.
RFC 2003 specifies a method to encapsulate an IPv4 datagram within another IPv4 datagram. The IP protocol number 4 is used to indicate the payload within a carrier IP packet is a passenger IPv4 packet. This vulnerability causes an affected device to unexpectedly decapsulate and process IP in IP packets destined to a locally configured IP address, even when no tunnel configuration is present.
Any input ACL configured on an inbound interface of the affected device is evaluated against the IP fields on the carrier IP packet prior to decapsulation; it would not be evaluated on the passenger IP packet. This may result in the passenger IP packet bypassing the intended ACL filtering. This may also allow the passenger IP packet to bypass other security boundaries that might be defined in the network path to the affected device in the presence of network filtering techniques that only inspect the outer IP header and not the inner IP packet.
Under specific conditions, processing of a crafted IP in IP packet could cause the network stack process to crash on an affected device. Repeated exploitation that causes the network stack process to restart multiple times could lead to a reload of the affected device, resulting in a DoS condition. A crash of the network stack process is followed by creation of a netstack core file on the device, which can be viewed by using the show cores CLI command (or dir cores on the local-mgmt CLI for Cisco UCS Fabric Interconnects). If a netstack core file is present, users should contact the Cisco Technical Assistance Center (TAC) to review the file and determine whether this vulnerability has been exploited on the device.
This vulnerability can only be triggered by IP in IP traffic destined to an affected device and cannot be exploited using traffic that transits an affected device. The vulnerability can only be triggered by IP in IP packets on which both the carrier and the passenger datagrams are IPv4. It cannot be triggered when either carrier, passenger, or both carrier and passenger are IPv6 datagrams, nor can it be triggered by any other tunneling protocol, including but not limited to Generic Routing Encapsulation (GRE).
In terms of a workaround, using infrastructure access control lists (iACLs) to allow only strictly required management and control plane traffic destined to the affected device, as recommended in the Cisco Guide to Securing NX-OS Software Devices, would prevent exploitation of this issue on Nexus devices.
Users may also consider explicitly denying all IP packets with protocol number 4 (corresponding to IP in IP packets) as part of their iACLs, if no legitimate IP in IP traffic is used in their network. A customized control plane policing (CoPP) policy may also be used to drop IP in IP traffic destined to an affected device; however, support for CoPP customization varies across different Nexus platforms and software releases. Customers are advised to contact their support organization for any assistance required with evaluating the feasibility of a workaround and with implementing a workaround on an affected device.
A vulnerability in the network stack of Cisco NX-OS Software could allow an unauthenticated, remote attacker to bypass certain security boundaries or cause a DoS condition on an affected device.
Cisco released software updates that address this vulnerability, according to an advisory.
This vulnerability affects the following Cisco products if they are running a vulnerable release of Cisco NX-OS Software:
- Nexus 1000 Virtual Edge for VMware vSphere (CSCvu10050)
- Nexus 1000V Switch for Microsoft Hyper-V (CSCvt67738)
- Nexus 1000V Switch for VMware vSphere (CSCvt67738)
- Nexus 3000 Series Switches (CSCun53663)
- Nexus 5500 Platform Switches (CSCvt67739)
- Nexus 5600 Platform Switches (CSCvt67739)
- Nexus 6000 Series Switches (CSCvt67739)
- Nexus 7000 Series Switches (CSCvt66624)
- Nexus 9000 Series Switches in standalone NX-OS mode (CSCun53663)
- UCS 6200 Series Fabric Interconnects (CSCvu03158)
- UCS 6300 Series Fabric Interconnects (CSCvt67740)

