A vulnerability in the ingress UDP packet processing functionality of Cisco Virtualized Packet Core−Distributed Instance (VPC−DI) Software could allow an unauthenticated, remote attacker to cause both control function (CF) instances on an affected system to reload, resulting in a denial of service (DoS) condition. The vulnerability is due to insufficient handling of user-supplied data by the affected software. An attacker could exploit this vulnerability by sending crafted UDP packets to the distributed instance (DI) network addresses of both CF instances on an affected system. A successful exploit could allow the attacker to cause an unhandled error condition on the affected system, which would cause the CF instances to reload and consequently cause the entire VPC to reload, resulting in the disconnection of all subscribers and a DoS condition on the affected system. This vulnerability can be exploited via IPv4 traffic only. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. This advisory is available at the following link: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20170621-vpc
This vulnerability affects Cisco Virtualized Packet Core−Distributed Instance (VPC−DI) Software running any release of the Cisco StarOS operating system prior to the first fixed release.
To determine whether a vulnerable release of Cisco StarOS is running on a VPC-DI instance, administrators can use the show version command in the device CLI. The following example shows the output of the command for a VPC−DI instance that is running Cisco StarOS Release 19.3.v5 (VPC−DI Release N4.2.5):
[local]VPC-001# show version
Active Software:
Image Version: 19.3.v5
Image Build Number: 65002
Image Description: Deployment_Build
Image Date: Wed Sep 14 05:35:14 EDT 2016
Boot Image: /flash/qvpc-di-19.3.v5.bin
No other Cisco products are currently known to be affected by this vulnerability.
Cisco has confirmed that this vulnerability does not affect the following Cisco products:
A DI network interconnects the virtual machines (VMs) in a VPC−DI instance to enable the VMs to communicate with each other. The DI network should be a unique, isolated network reserved for the exclusive use of a single VPC−DI instance. No other devices should be connected to the DI network. If more than one VPC−DI instance is instantiated in the same data center, each instance should have its own DI network.
To exploit this vulnerability, the attacker needs to be able to send UDP packets to the DI network interface of a VPC−DI instance via IPv4.
The vulnerable code exists only in VPC−DI Software. This vulnerability does not exist in Cisco VPC−SI Software or the other Cisco products listed in the “Products Confirmed Not Vulnerable” section.
Cisco has released free software updates that address the vulnerability described in this advisory. Customers may only install and expect support for software versions and feature sets for which they have purchased a license. By installing, downloading, accessing, or otherwise using such software upgrades, customers agree to follow the terms of the Cisco software license:
http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html
Additionally, customers may only download software for which they have a valid license, procured from Cisco directly, or through a Cisco authorized reseller or partner. In most cases this will be a maintenance upgrade to software that was previously purchased. Free security software updates do not entitle customers to a new software license, additional software feature sets, or major revision upgrades.
When considering software upgrades, customers are advised to regularly consult the advisories for Cisco products, which are available from the Cisco Security Advisories and Alerts page, to determine exposure and a complete upgrade solution.
In all cases, customers should ensure that the devices to be upgraded contain sufficient memory and confirm that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, customers are advised to contact the Cisco Technical Assistance Center (TAC) or their contracted maintenance providers.
Customers Without Service Contracts
Customers who purchase directly from Cisco but do not hold a Cisco service contract and customers who make purchases through third-party vendors but are unsuccessful in obtaining fixed software through their point of sale should obtain upgrades by contacting the Cisco TAC:
http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html
Customers should have the product serial number available and be prepared to provide the URL of this advisory as evidence of entitlement to a free upgrade.
Fixed Releases
In the following table, the first column lists major releases of Cisco VPC−DI Software and, parenthetically, the associated release of the Cisco StarOS operating system. The second and third columns indicate the first minor release that includes the fix for the Cisco bugs associated with this vulnerability. The fourth column indicates the recommended release to install to address this vulnerability.
Customers should upgrade to an appropriate release as indicated in the following table:
| Cisco VPC−DI Software and Cisco StarOS Major Release |
First Fixed Release for Cisco Bug CSCvc01665 |
First Fixed Release for Cisco Bug CSCvc35565 |
Recommended Release |
|---|---|---|---|
| N4.0 (19.2) | N4.2.6 (19.3.v6) |
N4.2.7 (19.3.v7) |
N4.2.7 (19.3.v7) or later |
| N4.2 (19.3) | N4.2.6 (19.3.v6) |
N4.2.7 (19.3.v7) |
N4.2.7 (19.3.v7) or later |
| N4.5 (20.0) | N4.7.2 (20.2.v2) |
N4.7.2 (20.2.v2) |
N4.7.2 (20.2.v2) or later |
| N4.6 (20.1) | N4.7.2 (20.2.v2) | N4.7.2 (20.2.v2) |
N4.7.2 (20.2.v2) or later |
| N4.7 (20.2) |
N4.7.2 (20.2.v2) |
N4.7.2 (20.2.v2) |
N4.7.2 (20.2.v2) or later |
| N5.0 (21.0) | Not affected |
N5.1 (21.1.v0) |
N5.1 (21.1.v0) or later |
| N5.1 (21.1) |
Not affected |
Not affected |
Not affected |
The Cisco Product Security Incident Response Team (PSIRT) is not aware of any public announcements or malicious use of the vulnerability that is described in this advisory.
This vulnerability was found during the resolution of a customer support case.
To learn about Cisco security vulnerability disclosure policies and publications, see the Security Vulnerability Policy. This document also contains instructions for obtaining fixed software and receiving security vulnerability information from Cisco.
| Version | Description | Section | Status | Date |
|---|---|---|---|---|
| 1.0 | Initial public release. | - | Final | 2017-June-21 |
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.
A standalone copy or paraphrase of the text of this document that omits the distribution URL is an uncontrolled copy and may lack important information or contain factual errors. The information in this document is intended for end users of Cisco products.
Vulmon