Advisory ID: cisco-sa-20140326-sip
Last Updated 2014 March 31 13:46 UTC (GMT)
For Public Release 2014 March 26 16:00 UTC (GMT)
Vulnerability Scoring Details
Software Versions and Fixes
Obtaining Fixed Software
Exploitation and Public Announcements
Status of This Notice: Final
Cisco Security Procedures
Cisco has released software updates that address this vulnerability.
There are no workarounds for devices that must run SIP; however, mitigations are available to limit exposure to this vulnerability.
This advisory is available at the following link:
Note: The March 26, 2014, Cisco IOS Software Security Advisory bundled publication includes six Cisco Security Advisories. All advisories address vulnerabilities in Cisco IOS Software. Each Cisco IOS Software Security Advisory lists the Cisco IOS Software releases that correct the vulnerability or vulnerabilities detailed in the advisory as well as the Cisco IOS Software releases that correct all Cisco IOS Software vulnerabilities in the March 2014 bundled publication.
Individual publication links are in Cisco Event Response: Semiannual Cisco IOS Software Security Advisory Bundled Publication at the following link:
- Cisco IOS Software release 15.3(3)M and 15.3(3)M1
- Cisco IOS XE Software release 3.10.0S, 3.10.0aS and 3.10.1S1
In addition to inspecting the Cisco IOS device configuration for a dial-peer command that causes the device to process SIP messages, administrators can also use the show processes | include SIP command to determine whether Cisco IOS Software is running the processes that handle SIP messages. In the following example, the presence of the process CCSIP_UDP_SOCKET or CCSIP_TCP_SOCKET indicates that the Cisco IOS device will process SIP messages:!
dial-peer voice <Voice dial-peer tag> voip
Note: Because there are several ways that a device running Cisco IOS Software or Cisco IOS XE Software can start processing SIP messages, it is recommended that the show processes | include SIP command be used to determine whether the device is processing SIP messages instead of relying on the presence of specific configuration commands.Router# show processes | include SIP 149 Mwe 40F48254 4 1 400023108/24000 0 CCSIP_UDP_SOCKET 150 Mwe 40F48034 4 1 400023388/24000 0 CCSIP_TCP_SOCKET
To determine the Cisco IOS Software release that is running on a Cisco product, administrators can log in to the device and issue the show version command to display the system banner. The system banner confirms that the device is running Cisco IOS Software by displaying text similar to "Cisco Internetwork Operating System Software" or "Cisco IOS Software." The image name displays in parentheses, followed by "Version" and the Cisco IOS Software release name. Other Cisco devices do not have the show version command or may provide different output.
The following example identifies a Cisco product that is running Cisco IOS Software Release 15.2(4)M5 with an installed image name of C3900-UNIVERSALK9-M:
Router> show version
Cisco IOS Software, C3900 Software (C3900-UNIVERSALK9-M), 15.2(4)M5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Fri 13-Sep-13 16:44 by prod_rel_team!--- output truncated
Additional information about Cisco IOS Software release naming conventions is available in White Paper: Cisco IOS and NX-OS Software Reference Guide.
A vulnerability in the SIP functionality of Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, remote attacker to trigger a device reload.
The vulnerability is due to incorrect processing of specific SIP messages. An attacker could exploit this vulnerability by sending specific SIP messages, which may be considered well formed or crafted to the SIP gateway. An exploit could allow the attacker to trigger a device reload.
This vulnerability is triggered when a device that is running an affected version of Cisco IOS Software or Cisco IOS XE Software processes the specific type of SIP messages. Only traffic destined to the device can trigger the vulnerability; transit SIP traffic is not an exploit vector. This vulnerability can be exploited with SIP over IP version 4 (IPv4) or IP version 6 (IPv6) communications protocol.
Note: In cases where SIP is running over TCP transport, a TCP three-way handshake is necessary to exploit this vulnerability.
This vulnerability is documented in Cisco bug ID CSCug45898 (registered customers only). This vulnerability has been assigned Common Vulnerabilities and Exposures (CVE) ID CVE-2014-2106
CVSS is a standards-based scoring method that conveys vulnerability severity and helps organizations determine the urgency and priority of a response.
Cisco has provided a base and temporal score. Customers can also compute environmental scores that help determine the impact of the vulnerability in their own networks.
Cisco has provided additional information regarding CVSS at the following link:
Cisco has also provided a CVSS calculator to compute the environmental impact for individual networks at the following link:
CSCug45898 - Cisco IOS Software and Cisco IOS XE Software Session Initiation Protocol Denial of Service Vulnerability
Calculate the environmental score of CSCug45898
CVSS Base Score - 7.8
CVSS Temporal Score - 6.4
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.
In February 2014, Cisco announced details of an industry-wide issue with memory components manufactured by a single supplier between 2005 and 2010. Although the majority of Cisco products that use these components are experiencing field failure rates below expected levels, a device reload or power cycle could expose component failures. While there are no known security implications associated with this issue, a subset of the affected products may experience a memory component failure during the software upgrade process. Cisco recommends customers review the related information and product-specific field notices at www.cisco.com/go/memory before making upgrade decisions. Each Field Notice indicates whether the product could experience the memory component failure during a software upgrade.
Cisco IOS Software
The Cisco IOS Software Checker is the quickest method to determine exposure to vulnerabilities in Cisco IOS Software. The tool allows customers to quickly identify Cisco Security Advisories that impact specific Cisco IOS Software releases. Users can initiate a search by selecting releases from the drop-down menu or uploading a file from their local system. The tool is also capable of parsing show version command output. Results can be customized by searching against all previously published Cisco Security Advisories, a specific publication, or all the advisories in the March 2014 Bundled Publication.
Customers can also use the Cisco IOS Software tables below to determine their exposure. Each row corresponds to a Cisco IOS Software release; if a particular release is vulnerable, the earliest releases that contain the fix are listed in the second column. The third column lists the earliest possible releases that correct all vulnerabilities in this Cisco IOS Software Security Advisory bundled publication.
Expand to View Detailed Fixed Software Information
|Major Release||Availability of Repaired Releases|
|Affected 12.X-Based Releases||First Fixed Release||First Fixed Release for All Advisories in the March 2014 Bundled Publication|
|There are no affected 12.X based releases|
|Affected 15.0-Based Releases||First Fixed Release||First Fixed Release for All Advisories in the March 2014 Bundled Publication|
|There are no affected 15.0 based releases|
|Affected 15.1-Based Releases||First Fixed Release||First Fixed Release for All Advisories in the March 2014 Bundled Publication|
|There are no affected 15.1 based releases|
|Affected 15.2-Based Releases||First Fixed Release||First Fixed Release for All Advisories in the March 2014 Bundled Publication|
|There are no affected 15.2 based releases|
|Affected 15.3-Based Releases||First Fixed Release||First Fixed Release for All Advisories in the March 2014 Bundled Publication|
Vulnerable; migrate to any release in 15.4T
Cisco IOS XE devices: Please see Cisco IOS XE Software Availability
Cisco IOS XE devices: Please see Cisco IOS XE Software Availability
|Affected 15.4-Based Releases||First Fixed Release||First Fixed Release for All Advisories in the March 2014 Bundled Publication|
|There are no affected 15.4 based releases|
Cisco IOS XE SoftwareOnly Cisco IOS XE Software release 3.10.0S, 3.10.0aS and 3.10.1S are affected by this vulnerability.
First fixed in Cisco IOS XE Software release 3.10.2S.
Cisco IOS XR SoftwareCisco IOS XR Software is not affected by any of the vulnerabilities that are disclosed in the March 2014 Cisco IOS Software Security Advisory bundled publications.
Additional mitigations that can be deployed on Cisco devices within the network are available in the companion document Identifying and Mitigating Exploitation of the Cisco IOS Software Session Initiation Protocol Denial of Service Vulnerability, which is available at the following link:
Disabling SIP Listening PortsFor devices that do not require SIP to be enabled, the simplest and most effective workaround is to disable SIP processing on the device. Some releases of Cisco IOS Software allow administrators to disable SIP with the following commands:
Warning: When applying this workaround to devices that are processing Media Gateway Control Protocol (MGCP) or H.323 calls, the device will not stop SIP processing while active calls are being processed. Under these circumstances, this workaround should be implemented during a maintenance window when active calls can be stopped briefly.sip-ua
no transport udp
no transport tcp
no transport tcp tls
The show udp connections, show tcp brief all, and show control-plane host open-ports commands can be used to confirm that the SIP UDP and TCP ports are closed after applying this workaround.
Depending on the Cisco IOS Software release in use, when SIP is disabled the output from the show ip sockets command may still show the SIP ports open, but sending traffic to them will cause the SIP process to display the following message:
*Nov 2 11:36:47.691: sip_udp_sock_process_read: SIP UDP Listener is DISABLED
Control Plane PolicingFor devices that need to offer SIP services, it is possible to use Control Plane Policing (CoPP) to block SIP traffic to the device from untrusted sources. Cisco IOS Releases 12.0S, 12.2SX, 12.2S, 12.3T, 12.4, and 12.4T support the CoPP feature. CoPP may be configured on a device to protect the management and control planes to minimize the risk and effectiveness of direct infrastructure attacks by explicitly permitting only authorized traffic sent to infrastructure devices in accordance with existing security policies and configurations. The following example can be adapted to specific network configurations:
Note: Because SIP can use UDP as a transport protocol, it is possible to spoof the source address of an IP packet, which may bypass access control lists that permit communication to these ports from trusted IP addresses. Additional information about Unicast Reverse Path Forwarding is at http://www.cisco.com/web/about/security/intelligence/unicast-rpf.html!– The 192.168.1.0/24 network and the 172.16.1.1 host are trusted. !– Everything else is not trusted. The following access list is used !– to determine what traffic needs to be dropped by a control plane !– policy (the CoPP feature): if the access list matches (permit) !– then traffic will be dropped and if the access list does not !– match (deny) then traffic will be processed by the router.
access-list 100 deny udp 192.168.1.0 0.0.0.255 any eq 5060 access-list 100 deny tcp 192.168.1.0 0.0.0.255 any eq 5060 access-list 100 deny tcp 192.168.1.0 0.0.0.255 any eq 5061 access-list 100 deny udp host 172.16.1.1 any eq 5060 access-list 100 deny tcp host 172.16.1.1 any eq 5060 access-list 100 deny tcp host 172.16.1.1 any eq 5061 access-list 100 permit udp any any eq 5060 access-list 100 permit tcp any any eq 5060 access-list 100 permit tcp any any eq 5061
!– Permit (police or drop)/deny (allow) all other Layer3 and Layer4 !– traffic in accordance with existing security policies and !– configurations for traffic that is authorized to be sent !– to infrastructure devices. !– Create a class map for traffic to be policed by !– the CoPP feature.
class-map match-all drop-sip-class match access-group 100
!– Create a policy map that will be applied to the !– control plane of the device.
policy-map control-plane-policy class drop-sip-class drop
!– Apply the policy map to the control plane of the !– device. control-plane service-policy input control-plane-policy
In the preceding CoPP example, the access control entries that match the potential exploit packets with the permit action cause these packets to be discarded by the policy map drop function, while packets that match the deny action (not shown) are not affected by the policy map drop function. Additional information about the configuration and use of the CoPP feature is at http://www.cisco.com/web/about/security/intelligence/coppwp_gs.html and http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gtrtlimt.html.
Customers may only install and expect support for feature sets they have purchased. By installing, downloading, accessing, or otherwise using such software upgrades, customers agree to follow the terms of the Cisco software license at http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html.
The effectiveness of any workaround or fix depends on specific customer situations, such as product mix, network topology, traffic behavior, and organizational mission. Because of the variety of affected products and releases, customers should consult their service providers or support organizations to ensure that any applied workaround or fix is the most appropriate in the intended network before it is deployed.
- +1 800 553 2447 (toll free from within North America)
- +1 408 526 7209 (toll call from anywhere in the world)
- email: email@example.com
Refer to Cisco Worldwide Contacts at http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html for additional TAC contact information, including localized telephone numbers, instructions, and email addresses for support in various languages.
This vulnerability was discovered during internal security testing.
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 stand-alone copy or Paraphrase of the text of this document that omits the distribution URL in the following section is an uncontrolled copy, and may lack important information or contain factual errors.
Additionally, a text version of this advisory is clear signed with the Cisco PSIRT PGP key and circulated among the following email addresses:
|Revision 1.1||2014-March-31||Added Cisco IOS XE Release 3.10.0aS as an affected release.|
|Revision 1.0||2014-March-26||Initial public release.|