VAR-200909-0387
Vulnerability from variot - Updated: 2025-04-10 22:06Unspecified vulnerability in Cisco IOS 12.2 through 12.4, when the Cisco Unified Border Element feature is enabled, allows remote attackers to cause a denial of service (device reload) via crafted SIP messages, aka Bug ID CSCsx25880. The problem is Bug ID : CSCsx25880 It is a problem.Cleverly crafted SIP Service disruption by message (DoS) There is a possibility of being put into a state. Cisco IOS is prone to a denial-of-service vulnerability. An attacker can exploit this issue to cause an affected device to crash and reload, denying service to legitimate users. This issue is tracked by Cisco Bug ID CSCsx25880.
Cisco has released free software updates that address this vulnerability. For devices that must run SIP there are no workarounds; however, mitigations are available to limit exposure of the vulnerability.
This advisory is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml
Note: The September 23, 2009, Cisco IOS Security Advisory bundled publication includes eleven Security Advisories. Each advisory lists the releases that correct the vulnerability or vulnerabilities detailed in the advisory. The following table lists releases that correct all Cisco IOS Software vulnerabilities that have been published on September 23, 2009, or earlier.
http://www.cisco.com/warp/public/707/cisco-sa-20090923-bundle.shtml
Individual publication links are in "Cisco Event Response: Semiannual Cisco IOS Software Advisory Bundled Publication" at the following link:
http://www.cisco.com/web/about/security/intelligence/Cisco_ERP_sep09.html
Affected Products
This vulnerability only affects devices running Cisco IOS Software with SIP voice services enabled. It provides a network-to-network interface point for billing, security, call admission control, quality of service, and signaling interworking. An example of an affected configuration is as follows:
voice service voip
allow-connections from-type to to-type
...
!
Recent versions of Cisco IOS Software do not process SIP messages by default. Creating a dial peer by issuing the command "dial-peer voice" will start the SIP processes, causing the Cisco IOS device to process SIP messages. In addition, several features within Cisco Unified Communications Manager Express, such as ePhones, once configured will also automatically start the SIP process, which will cause the device to start processing SIP messages. An example of an affected configuration is as follows:
dial-peer voice <Voice dial-peer tag> voip
...
!
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 command show processes | include SIP to determine whether Cisco IOS Software is running the processes that handle SIP messages. In the following example, the presence of the processes CCSIP_UDP_SOCKET or CCSIP_TCP_SOCKET indicates that the Cisco IOS device is processing SIP messages:
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
warning Warning: Since there are several ways a device running Cisco IOS 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.
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 12.3(26) with an installed image name of C2500-IS-L:
Router#show version
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-IS-L), Version 12.3(26), RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Mon 17-Mar-08 14:39 by dchih
!--- output truncated
The following example identifies a Cisco product that is running Cisco IOS Software Release 12.4(20)T with an installed image name of C1841-ADVENTERPRISEK9-M:
Router#show version
Cisco IOS Software, 1841 Software (C1841-ADVENTERPRISEK9-M), Version 12.4(20)T, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 10-Jul-08 20:25 by prod_rel_team
!--- output truncated
Additional information about Cisco IOS Software release naming conventions is available in "White Paper: Cisco IOS Reference Guide" at the following link:
http://www.cisco.com/warp/public/620/1.html
Products Confirmed Not Vulnerable +--------------------------------
The SIP Application Layer Gateway (ALG), which is used by the Cisco IOS NAT and firewall features of Cisco IOS Software, is not affected by this vulnerability. No other Cisco products are currently known to be affected by this vulnerability.
Details
SIP is a popular signaling protocol that is used to manage voice and video calls across IP networks such as the Internet. SIP is responsible for handling all aspects of call setup and termination. Voice and video are the most popular types of sessions that SIP handles, but the protocol has the flexibility to accommodate other applications that require call setup and termination. SIP call signaling can use UDP (port 5060), TCP (port 5060), or TLS (TCP port 5061) as the underlying transport protocol. It provides a network-to-network interface point for billing, security, call admission control, quality of service, and signaling interworking. This vulnerability is triggered by processing a series of crafted SIP messages.
Vulnerability Scoring Details
Cisco has provided scores for the vulnerability in this advisory based on the Common Vulnerability Scoring System (CVSS). The CVSS scoring in this Security Advisory is done in accordance with CVSS version 2.0.
CVSS is a standards-based scoring method that conveys vulnerability severity and helps determine urgency and priority of response.
Cisco has provided a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks.
Cisco has provided an FAQ to answer additional questions regarding CVSS at:
http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html
Cisco has also provided a CVSS calculator to help compute the environmental impact for individual networks at:
http://intellishield.cisco.com/security/alertmanager/cvss
CSCsx25880 - Crafted SIP packet may cause device reload
CVSS Base Score - 7.8
Access Vector - Network Access Complexity - Low Authentication - None Confidentiality Impact - None Integrity Impact - None Availability Impact - Complete
CVSS Temporal Score - 6.4
Exploitability - Functional Remediation Level - Official-Fix Report Confidence - Confirmed
Impact
Successful exploitation of the vulnerability described in this document may result in a reload of the device. The issue could be repeatedly exploited to cause an extended DoS condition.
Software Versions and Fixes
When considering software upgrades, also consult:
http://www.cisco.com/go/psirt
and any subsequent advisories to determine exposure and a complete upgrade solution.
In all cases, customers should exercise caution to be certain the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco Technical Assistance Center (TAC) or your contracted maintenance provider for assistance. If a given release train is vulnerable, then the earliest possible releases that contain the fix (along with the anticipated date of availability for each, if applicable) are listed in the "First Fixed Release" column of the table. The "Recommended Release" column indicates the releases which have fixes for all the published vulnerabilities at the time of this Advisory. A device running a release in the given train that is earlier than the release in a specific column (less than the First Fixed Release) is known to be vulnerable. Cisco recommends upgrading to a release equal to or later than the release in the "Recommended Releases" column of the table.
+-------------------------------------------------------------------+ | Major | Availability of Repaired Releases | | Release | | |------------+------------------------------------------------------| | Affected | | Recommended | | 12.0-Based | First Fixed Release | Release | | Releases | | | |-------------------------------------------------------------------| | There are no affected 12.0 based releases. | |-------------------------------------------------------------------| | Affected | | Recommended | | 12.1-Based | First Fixed Release | Release | | Releases | | | |-------------------------------------------------------------------| | There are no affected 12.1 based releases. | |-------------------------------------------------------------------| | Affected | | Recommended | | 12.2-Based | First Fixed Release | Release | | Releases | | | |-------------------------------------------------------------------| | There are no affected 12.2 based releases. | |-------------------------------------------------------------------| | Affected | | Recommended | | 12.3-Based | First Fixed Release | Release | | Releases | | | |------------+---------------------------------------+--------------| | 12.3 | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3B | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3BC | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3BW | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3EU | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3JA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3JEA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3JEB | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3JEC | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3JK | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3JL | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3JX | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3T | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3TPC | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3VA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XB | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XC | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XD | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XE | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XF | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XG | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XI | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XJ | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XK | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XL | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XQ | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XR | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XS | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XU | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XW | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XX | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XY | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3XZ | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YD | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YF | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YG | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YH | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YI | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YJ | Not Vulnerable | | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | Releases prior to 12.3(11)YK3 are | 12.4(20)T4 | | | vulnerable, release 12.3(11)YK3 and | | | 12.3YK | later are not vulnerable; first fixed | 12.4(22)T3 | | | in 12.4T | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | 12.3YM | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YQ | Not Vulnerable | | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | Vulnerable; first fixed in 12.4T | 12.4(20)T4 | | | | | | 12.3YS | Releases up to and including 12.3(11) | 12.4(22)T3 | | | YS1 are not vulnerable. | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.3YT | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | 12.3YU | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YX | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3YZ | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.3ZA | Not Vulnerable | | |------------+---------------------------------------+--------------| | Affected | | Recommended | | 12.4-Based | First Fixed Release | Release | | Releases | | | |------------+---------------------------------------+--------------| | 12.4 | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4GC | 12.4(24)GC1 | | |------------+---------------------------------------+--------------| | 12.4JA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4JDA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4JDC | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4JDD | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4JK | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4JL | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4JMA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4JMB | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4JX | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4MD | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4MDA | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4MR | 12.4(19)MR3 | 12.4(19)MR3 | |------------+---------------------------------------+--------------| | 12.4SW | Not Vulnerable | | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | 12.4(24)T1 | | | | | 12.4(20)T4 | | | 12.4(15)T10 | | | 12.4T | | 12.4(22)T3 | | | 12.4(20)T3 | | | | | 12.4(24)T2; | | | 12.4(22)T2 | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XA | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XB | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XC | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XD | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XE | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | 12.4XF | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4XG | Not Vulnerable | | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XJ | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | 12.4XK | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4XL | 12.4(15)XL5 | | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | Vulnerable; first fixed in 12.4T | 12.4(20)T4 | | | | | | 12.4XM | Releases up to and including 12.4(15) | 12.4(22)T3 | | | XM are not vulnerable. | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | 12.4XN | Not Vulnerable | | |------------+---------------------------------------+--------------| | | Vulnerable; Contact your support | | | 12.4XP | organization per the instructions in | | | | Obtaining Fixed Software section of | | | | this advisory | | |------------+---------------------------------------+--------------| | 12.4XQ | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4XR | Not Vulnerable | | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XT | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | Vulnerable; Contact your support | | | 12.4XV | organization per the instructions in | | | | Obtaining Fixed Software section of | | | | this advisory | | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XW | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XY | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4XZ | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | | | 12.4(15)T10 | | | | | | | | 12.4(20)T4 | | | | | | 12.4YA | Vulnerable; first fixed in 12.4T | 12.4(22)T3 | | | | | | | | 12.4(24)T2; | | | | Available on | | | | 23-OCT-2009 | |------------+---------------------------------------+--------------| | 12.4YB | 12.4(22)YB1 | 12.4(22)YB4 | |------------+---------------------------------------+--------------| | 12.4YD | Not Vulnerable | | |------------+---------------------------------------+--------------| | 12.4YE | Not Vulnerable | | +-------------------------------------------------------------------+
Note: No Cisco IOS-XE or Cisco IOS Software Modularity releases are affected by this vulnerability.
Workarounds
If the affected Cisco IOS device requires SIP for VoIP services, SIP cannot be disabled, and therefore, no workarounds are available. Users are advised to apply mitigation techniques to help limit exposure to the vulnerability. Mitigation consists of allowing only legitimate devices to connect to the routers. To increase effectiveness, the mitigation must be coupled with anti-spoofing measures on the network edge. This action is required because SIP can use UDP as the transport protocol. Some versions of Cisco IOS Software allow administrators to accomplish this with the following commands:
sip-ua
no transport udp
no transport tcp
no transport tcp tls
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 briefly stopped.
The "show udp connections", "show tcp brief all", and "show processes | include SIP" 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 version in use, the output of "show ip sockets" still showed UDP port 5060 open, but sending something to that port caused the SIP process to emit the following message:
*Feb 2 11:36:47.691: sip_udp_sock_process_read: SIP UDP Listener is
DISABLED
Control Plane Policing +---------------------
For 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. 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 the network
!-- 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 drop-sip-traffic
class drop-sip-class
drop
!-- Apply the Policy-Map to the Control-Plane of the
!-- device.
control-plane
service-policy input drop-sip-traffic
Warning: Because SIP can use UDP as a transport protocol, it is possible to easily spoof the IP address of the sender, which may defeat access control lists that permit communication to these ports from trusted IP addresses.
In the above CoPP example, the access control entries (ACEs) that match the potential exploit packets with the "permit" action result in these packets being 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 on the configuration and use of the CoPP feature can be found 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
Obtaining Fixed Software
Cisco has released free software updates that address these vulnerabilities. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues specific to their environment.
Customers may only install and expect support for the feature sets they have purchased. By installing, downloading, accessing or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco's software license terms found at:
http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html
or as otherwise set forth at Cisco.com Downloads at:
http://www.cisco.com/public/sw-center/sw-usingswc.shtml
Do not contact psirt@cisco.com or security-alert@cisco.com for software upgrades.
Customers with Service Contracts +-------------------------------
Customers with contracts should obtain upgraded software through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on Cisco's worldwide website at http://www.cisco.com.
Customers using Third Party Support Organizations +------------------------------------------------
Customers whose Cisco products are provided or maintained through prior or existing agreements with third-party support organizations, such as Cisco Partners, authorized resellers, or service providers should contact that support organization for guidance and assistance with the appropriate course of action in regards to this advisory.
The effectiveness of any workaround or fix is dependent on specific customer situations, such as product mix, network topology, traffic behavior, and organizational mission. Due to the variety of affected products and releases, customers should consult with their service provider or support organization to ensure any applied workaround or fix is the most appropriate for use in the intended network before it is deployed.
Customers without Service Contracts +----------------------------------
Customers who purchase direct from Cisco but do not hold a Cisco service contract, and customers who purchase through third-party vendors but are unsuccessful in obtaining fixed software through their point of sale should acquire upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows.
- +1 800 553 2447 (toll free from within North America)
- +1 408 526 7209 (toll call from anywhere in the world)
- e-mail: tac@cisco.com
Customers should have their product serial number available and be prepared to give the URL of this notice as evidence of entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC.
Refer to:
http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html
for additional TAC contact information, including localized telephone numbers, and instructions and e-mail addresses for use in various languages.
Exploitation and Public Announcements
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory.
This vulnerability was discovered during internal testing.
Status of this Notice: FINAL
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.
Distribution
This advisory is posted on Cisco's worldwide website at:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml
In addition to worldwide web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and is posted to the following e-mail and Usenet news recipients.
- cust-security-announce@cisco.com
- first-bulletins@lists.first.org
- bugtraq@securityfocus.com
- vulnwatch@vulnwatch.org
- cisco@spot.colorado.edu
- cisco-nsp@puck.nether.net
- full-disclosure@lists.grok.org.uk
- comp.dcom.sys.cisco@newsgate.cisco.com
Future updates of this advisory, if any, will be placed on Cisco's worldwide website, but may or may not be actively announced on mailing lists or newsgroups. Users concerned about this problem are encouraged to check the above URL for any updates.
Revision History
+----------------------------------------+ | Revision | | Initial | | 1.0 | 2009-September-23 | public | | | | release | +----------------------------------------+
Cisco Security Procedures
Complete information on reporting security vulnerabilities in Cisco products, obtaining assistance with security incidents, and registering to receive security information from Cisco, is available on Cisco's worldwide website at:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
This includes instructions for press inquiries regarding Cisco security notices. All Cisco security advisories are available at:
http://www.cisco.com/go/psirt -----BEGIN PGP SIGNATURE-----
iD8DBQFKukGZ86n/Gc8U/uARAh54AJ4jQJCLVMauxJXj00WMu822+kH1TQCfTzA6 2++Xtx6BvyycWfoy75Zjtx0= =nUyE -----END PGP SIGNATURE-----
. ----------------------------------------------------------------------
Do you have VARM strategy implemented?
(Vulnerability Assessment Remediation Management)
If not, then implement it through the most reliable vulnerability intelligence source on the market.
Implement it through Secunia. This can be exploited to cause a buffer overflow via specially crafted HTTP requests.
Successful exploitation may allow execution of arbitrary code.
2) An error in the IKE implementation can be exploited to allocate all available Phase 1 SAs and prevent new IPSec sessions from being established.
Successful exploitation requires that the IKE certificate based authentication method is used.
3) Multiple errors exist in the IP tunnelling implementation when switching network packets. These can be exploited to trigger a device reload via specially crafted packets.
Successful exploitation requires that the device is configured for PPTP, GRE, IPinIP, Generic Packet Tunneling in IPv6, or IPv6 over IP tunnels, and Cisco Express Forwarding.
4) An error in the implementation of the Object Groups for ACLs feature can be exploited to bypass access control policies.
5) An error in the H.323 implementation can be exploited to trigger a device reload via specially crafted TCP packets.
Successful exploitation requires that H.323 is enabled (disabled by default).
For more information: SA36836
7) An error in the SSLVPN, SSH, and IKE Encrypted Nonces features can be exploited to reload a device via specially crafted packets sent to TCP ports 22 (for SSH) or 443 (for SSLVPN), or UDP ports 500 and 4500 (for IKE Encrypted Nonces).
8) A race condition error exists in the Authentication Proxy for HTTP(S), Web Authentication, and consent features. This can be exploited to bypass the authentication proxy services and the consent accept web page if a successfully authenticated session or accepted consent session exists. This can be exploited to reload a device via a specially crafted SIP transit packet.
10) An error exists in the NTPv4 implementation while creating NTP reply packets. This can be exploited to trigger a device reload via a specially crafted NTP packet.
SOLUTION: Update to a fixed version (please see the vendor's advisories for details).
PROVIDED AND/OR DISCOVERED BY: 1, 3-10) Reported by the vendor. 2) Reported to the vendor by a customer.
ORIGINAL ADVISORY: http://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-h323.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-ios-fw.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-ntp.shtml
OTHER REFERENCES: SA36836: http://secunia.com/advisories/36836/
About: This Advisory was delivered by Secunia as a free service to help everybody keeping their systems up to date against the latest vulnerabilities.
Subscribe: http://secunia.com/advisories/secunia_security_advisories/
Definitions: (Criticality, Where etc.) http://secunia.com/advisories/about_secunia_advisories/
Please Note: Secunia recommends that you verify all advisories you receive by clicking the link. Secunia NEVER sends attached files with advisories. Secunia does not advise people to install third party patches, only use those supplied by the vendor.
Unsubscribe: Secunia Security Advisories http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org
Show details on source website
{
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
"affected_products": {
"@id": "https://www.variotdbs.pl/ref/affected_products"
},
"configurations": {
"@id": "https://www.variotdbs.pl/ref/configurations"
},
"credits": {
"@id": "https://www.variotdbs.pl/ref/credits"
},
"cvss": {
"@id": "https://www.variotdbs.pl/ref/cvss/"
},
"description": {
"@id": "https://www.variotdbs.pl/ref/description/"
},
"exploit_availability": {
"@id": "https://www.variotdbs.pl/ref/exploit_availability/"
},
"external_ids": {
"@id": "https://www.variotdbs.pl/ref/external_ids/"
},
"iot": {
"@id": "https://www.variotdbs.pl/ref/iot/"
},
"iot_taxonomy": {
"@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
},
"patch": {
"@id": "https://www.variotdbs.pl/ref/patch/"
},
"problemtype_data": {
"@id": "https://www.variotdbs.pl/ref/problemtype_data/"
},
"references": {
"@id": "https://www.variotdbs.pl/ref/references/"
},
"sources": {
"@id": "https://www.variotdbs.pl/ref/sources/"
},
"sources_release_date": {
"@id": "https://www.variotdbs.pl/ref/sources_release_date/"
},
"sources_update_date": {
"@id": "https://www.variotdbs.pl/ref/sources_update_date/"
},
"threat_type": {
"@id": "https://www.variotdbs.pl/ref/threat_type/"
},
"title": {
"@id": "https://www.variotdbs.pl/ref/title/"
},
"type": {
"@id": "https://www.variotdbs.pl/ref/type/"
}
},
"@id": "https://www.variotdbs.pl/vuln/VAR-200909-0387",
"affected_products": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/affected_products#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"model": "ios",
"scope": "eq",
"trust": 1.9,
"vendor": "cisco",
"version": "12.4xv"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4xw"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4xl"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4xy"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4xe"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4xp"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4xt"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4xm"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4ya"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.4xz"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4mr"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.3yk"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.3ys"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4xc"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4gc"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4xd"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4t"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4xa"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.3yt"
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.3"
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.4"
},
{
"model": "ios 12.4yb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4ya",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xz",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xy",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xw",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xt",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xp",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xm",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xl",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xj",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xe",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xd",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xa",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4t",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4mr",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4gc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yt",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3ys",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yk",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 t1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 gc1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 yb1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 t2",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 t3",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 mr3",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 xm",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 xl5",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 t10",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3 ys1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3 yk3",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
}
],
"sources": [
{
"db": "BID",
"id": "36499"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002160"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
},
{
"db": "NVD",
"id": "CVE-2009-2870"
}
]
},
"configurations": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/configurations#",
"children": {
"@container": "@list"
},
"cpe_match": {
"@container": "@list"
},
"data": {
"@container": "@list"
},
"nodes": {
"@container": "@list"
}
},
"data": [
{
"CVE_data_version": "4.0",
"nodes": [
{
"cpe_match": [
{
"cpe22Uri": "cpe:/o:cisco:ios",
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002160"
}
]
},
"credits": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/credits#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Cisco Security bulletin",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
}
],
"trust": 0.6
},
"cve": "CVE-2009-2870",
"cvss": {
"@context": {
"cvssV2": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
},
"cvssV3": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
},
"severity": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/cvss/severity#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/severity"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"cvssV2": [
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "nvd@nist.gov",
"availabilityImpact": "COMPLETE",
"baseScore": 7.8,
"confidentialityImpact": "NONE",
"exploitabilityScore": 10.0,
"id": "CVE-2009-2870",
"impactScore": 6.9,
"integrityImpact": "NONE",
"severity": "HIGH",
"trust": 1.8,
"vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:C",
"version": "2.0"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "COMPLETE",
"baseScore": 7.8,
"confidentialityImpact": "NONE",
"exploitabilityScore": 10.0,
"id": "VHN-40316",
"impactScore": 6.9,
"integrityImpact": "NONE",
"severity": "HIGH",
"trust": 0.1,
"vectorString": "AV:N/AC:L/AU:N/C:N/I:N/A:C",
"version": "2.0"
}
],
"cvssV3": [],
"severity": [
{
"author": "nvd@nist.gov",
"id": "CVE-2009-2870",
"trust": 1.0,
"value": "HIGH"
},
{
"author": "NVD",
"id": "CVE-2009-2870",
"trust": 0.8,
"value": "High"
},
{
"author": "CNNVD",
"id": "CNNVD-200910-024",
"trust": 0.6,
"value": "HIGH"
},
{
"author": "VULHUB",
"id": "VHN-40316",
"trust": 0.1,
"value": "HIGH"
}
]
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40316"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002160"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
},
{
"db": "NVD",
"id": "CVE-2009-2870"
}
]
},
"description": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/description#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Unspecified vulnerability in Cisco IOS 12.2 through 12.4, when the Cisco Unified Border Element feature is enabled, allows remote attackers to cause a denial of service (device reload) via crafted SIP messages, aka Bug ID CSCsx25880. The problem is Bug ID : CSCsx25880 It is a problem.Cleverly crafted SIP Service disruption by message (DoS) There is a possibility of being put into a state. Cisco IOS is prone to a denial-of-service vulnerability. \nAn attacker can exploit this issue to cause an affected device to crash and reload, denying service to legitimate users. \nThis issue is tracked by Cisco Bug ID CSCsx25880. \n\nCisco has released free software updates that address this\nvulnerability. For devices that must run SIP there are no\nworkarounds; however, mitigations are available to limit exposure of\nthe vulnerability. \n\nThis advisory is posted at:\n\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml\n\nNote: The September 23, 2009, Cisco IOS Security Advisory bundled\npublication includes eleven Security Advisories. Each advisory lists the releases that correct the\nvulnerability or vulnerabilities detailed in the advisory. The\nfollowing table lists releases that correct all Cisco IOS Software\nvulnerabilities that have been published on September 23, 2009, or\nearlier. \n\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-bundle.shtml\n\nIndividual publication links are in \"Cisco Event Response: Semiannual\nCisco IOS Software Advisory Bundled Publication\" at the following\nlink:\n\nhttp://www.cisco.com/web/about/security/intelligence/Cisco_ERP_sep09.html\n\nAffected Products\n=================\n\nThis vulnerability only affects devices running Cisco IOS Software\nwith SIP voice services enabled. It provides\na network-to-network interface point for billing, security, call\nadmission control, quality of service, and signaling interworking. An example of an\naffected configuration is as follows:\n\n voice service voip\n allow-connections from-type to to-type \n ... \n !\n\nRecent versions of Cisco IOS Software do not process SIP messages by\ndefault. Creating a dial peer by issuing the command \"dial-peer voice\"\nwill start the SIP processes, causing the Cisco IOS device to process\nSIP messages. In addition, several features within Cisco Unified\nCommunications Manager Express, such as ePhones, once configured will\nalso automatically start the SIP process, which will cause the device\nto start processing SIP messages. An example of an affected\nconfiguration is as follows:\n\n dial-peer voice \u003cVoice dial-peer tag\u003e voip\n ... \n !\n\nIn addition to inspecting the Cisco IOS device configuration for a\ndial-peer command that causes the device to process SIP messages,\nadministrators can also use the command show processes | include SIP\nto determine whether Cisco IOS Software is running the processes that\nhandle SIP messages. In the following example, the presence of the\nprocesses CCSIP_UDP_SOCKET or CCSIP_TCP_SOCKET indicates that the\nCisco IOS device is processing SIP messages:\n\n Router#show processes | include SIP\n 149 Mwe 40F48254 4 1 400023108/24000 0 CCSIP_UDP_SOCKET\n 150 Mwe 40F48034 4 1 400023388/24000 0 CCSIP_TCP_SOCKET\n\nwarning Warning: Since there are several ways a device running Cisco\nIOS Software can start processing SIP messages, it is recommended\nthat the \"show processes | include SIP\" command be used to determine\nwhether the device is processing SIP messages instead of relying on\nthe presence of specific configuration commands. \n\nTo determine the Cisco IOS Software release that is running on a\nCisco product, administrators can log in to the device and issue the\nshow version command to display the system banner. The system banner\nconfirms that the device is running Cisco IOS Software by displaying\ntext similar to \"Cisco Internetwork Operating System Software\" or\n\"Cisco IOS Software.\" The image name displays in parentheses,\nfollowed by \"Version\" and the Cisco IOS Software release name. Other\nCisco devices do not have the show version command or may provide\ndifferent output. \n\nThe following example identifies a Cisco product that is running\nCisco IOS Software Release 12.3(26) with an installed image name of\nC2500-IS-L:\n\n Router#show version\n Cisco Internetwork Operating System Software\n IOS (tm) 2500 Software (C2500-IS-L), Version 12.3(26), RELEASE SOFTWARE (fc2)\n Technical Support: http://www.cisco.com/techsupport\n Copyright (c) 1986-2008 by cisco Systems, Inc. \n Compiled Mon 17-Mar-08 14:39 by dchih\n \n \n !--- output truncated\n \n\nThe following example identifies a Cisco product that is running\nCisco IOS Software Release 12.4(20)T with an installed image name of\nC1841-ADVENTERPRISEK9-M:\n\n Router#show version\n Cisco IOS Software, 1841 Software (C1841-ADVENTERPRISEK9-M), Version 12.4(20)T, RELEASE SOFTWARE (fc3)\n Technical Support: http://www.cisco.com/techsupport\n Copyright (c) 1986-2008 by Cisco Systems, Inc. \n Compiled Thu 10-Jul-08 20:25 by prod_rel_team\n \n \n !--- output truncated\n \n\nAdditional information about Cisco IOS Software release naming\nconventions is available in \"White Paper: Cisco IOS Reference Guide\"\nat the following link:\n\nhttp://www.cisco.com/warp/public/620/1.html\n\nProducts Confirmed Not Vulnerable\n+--------------------------------\n\nThe SIP Application Layer Gateway (ALG), which is used by the Cisco\nIOS NAT and firewall features of Cisco IOS Software, is not affected\nby this vulnerability. No other Cisco\nproducts are currently known to be affected by this vulnerability. \n\nDetails\n=======\n\nSIP is a popular signaling protocol that is used to manage voice and\nvideo calls across IP networks such as the Internet. SIP is\nresponsible for handling all aspects of call setup and termination. \nVoice and video are the most popular types of sessions that SIP\nhandles, but the protocol has the flexibility to accommodate other\napplications that require call setup and termination. SIP call\nsignaling can use UDP (port 5060), TCP (port 5060), or TLS (TCP port\n5061) as the underlying transport protocol. It provides a\nnetwork-to-network interface point for billing, security, call\nadmission control, quality of service, and signaling interworking. This vulnerability is triggered\nby processing a series of crafted SIP messages. \n\nVulnerability Scoring Details\n=============================\n\nCisco has provided scores for the vulnerability in this advisory\nbased on the Common Vulnerability Scoring System (CVSS). The CVSS\nscoring in this Security Advisory is done in accordance with CVSS\nversion 2.0. \n\nCVSS is a standards-based scoring method that conveys vulnerability\nseverity and helps determine urgency and priority of response. \n\nCisco has provided a base and temporal score. Customers can then\ncompute environmental scores to assist in determining the impact of\nthe vulnerability in individual networks. \n\nCisco has provided an FAQ to answer additional questions regarding\nCVSS at:\n\nhttp://www.cisco.com/web/about/security/intelligence/cvss-qandas.html\n\nCisco has also provided a CVSS calculator to help compute the\nenvironmental impact for individual networks at:\n\nhttp://intellishield.cisco.com/security/alertmanager/cvss\n\nCSCsx25880 - Crafted SIP packet may cause device reload\n\nCVSS Base Score - 7.8\n\nAccess Vector - Network\nAccess Complexity - Low\nAuthentication - None\nConfidentiality Impact - None\nIntegrity Impact - None\nAvailability Impact - Complete\n\nCVSS Temporal Score - 6.4\n\nExploitability - Functional\nRemediation Level - Official-Fix\nReport Confidence - Confirmed\n\nImpact\n======\n\nSuccessful exploitation of the vulnerability described in this\ndocument may result in a reload of the device. The issue could be\nrepeatedly exploited to cause an extended DoS condition. \n\nSoftware Versions and Fixes\n===========================\n\nWhen considering software upgrades, also consult:\n\nhttp://www.cisco.com/go/psirt\n\nand any subsequent advisories to determine exposure and a complete\nupgrade solution. \n\nIn all cases, customers should exercise caution to be certain the\ndevices to be upgraded contain sufficient memory and that current\nhardware and software configurations will continue to be supported\nproperly by the new release. If the information is not clear, contact\nthe Cisco Technical Assistance Center (TAC) or your contracted\nmaintenance provider for assistance. If a given release train is vulnerable, then the\nearliest possible releases that contain the fix (along with the\nanticipated date of availability for each, if applicable) are listed\nin the \"First Fixed Release\" column of the table. The \"Recommended\nRelease\" column indicates the releases which have fixes for all the\npublished vulnerabilities at the time of this Advisory. A device\nrunning a release in the given train that is earlier than the release\nin a specific column (less than the First Fixed Release) is known to\nbe vulnerable. Cisco recommends upgrading to a release equal to or\nlater than the release in the \"Recommended Releases\" column of the\ntable. \n\n+-------------------------------------------------------------------+\n| Major | Availability of Repaired Releases |\n| Release | |\n|------------+------------------------------------------------------|\n| Affected | | Recommended |\n| 12.0-Based | First Fixed Release | Release |\n| Releases | | |\n|-------------------------------------------------------------------|\n| There are no affected 12.0 based releases. |\n|-------------------------------------------------------------------|\n| Affected | | Recommended |\n| 12.1-Based | First Fixed Release | Release |\n| Releases | | |\n|-------------------------------------------------------------------|\n| There are no affected 12.1 based releases. |\n|-------------------------------------------------------------------|\n| Affected | | Recommended |\n| 12.2-Based | First Fixed Release | Release |\n| Releases | | |\n|-------------------------------------------------------------------|\n| There are no affected 12.2 based releases. |\n|-------------------------------------------------------------------|\n| Affected | | Recommended |\n| 12.3-Based | First Fixed Release | Release |\n| Releases | | |\n|------------+---------------------------------------+--------------|\n| 12.3 | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3B | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3BC | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3BW | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3EU | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3JA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3JEA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3JEB | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3JEC | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3JK | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3JL | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3JX | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3T | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3TPC | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3VA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XB | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XC | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XD | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XE | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XF | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XG | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XI | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XJ | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XK | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XL | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XQ | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XR | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XS | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XU | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XW | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XX | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XY | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3XZ | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YD | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YF | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YG | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YH | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YI | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YJ | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | Releases prior to 12.3(11)YK3 are | 12.4(20)T4 |\n| | vulnerable, release 12.3(11)YK3 and | |\n| 12.3YK | later are not vulnerable; first fixed | 12.4(22)T3 |\n| | in 12.4T | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| 12.3YM | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YQ | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | Vulnerable; first fixed in 12.4T | 12.4(20)T4 |\n| | | |\n| 12.3YS | Releases up to and including 12.3(11) | 12.4(22)T3 |\n| | YS1 are not vulnerable. | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.3YT | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| 12.3YU | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YX | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3YZ | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.3ZA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| Affected | | Recommended |\n| 12.4-Based | First Fixed Release | Release |\n| Releases | | |\n|------------+---------------------------------------+--------------|\n| 12.4 | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4GC | 12.4(24)GC1 | |\n|------------+---------------------------------------+--------------|\n| 12.4JA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4JDA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4JDC | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4JDD | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4JK | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4JL | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4JMA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4JMB | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4JX | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4MD | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4MDA | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4MR | 12.4(19)MR3 | 12.4(19)MR3 |\n|------------+---------------------------------------+--------------|\n| 12.4SW | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | 12.4(24)T1 | |\n| | | 12.4(20)T4 |\n| | 12.4(15)T10 | |\n| 12.4T | | 12.4(22)T3 |\n| | 12.4(20)T3 | |\n| | | 12.4(24)T2; |\n| | 12.4(22)T2 | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XA | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XB | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XC | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XD | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XE | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| 12.4XF | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4XG | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XJ | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| 12.4XK | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4XL | 12.4(15)XL5 | |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | Vulnerable; first fixed in 12.4T | 12.4(20)T4 |\n| | | |\n| 12.4XM | Releases up to and including 12.4(15) | 12.4(22)T3 |\n| | XM are not vulnerable. | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| 12.4XN | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| | Vulnerable; Contact your support | |\n| 12.4XP | organization per the instructions in | |\n| | Obtaining Fixed Software section of | |\n| | this advisory | |\n|------------+---------------------------------------+--------------|\n| 12.4XQ | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4XR | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XT | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | Vulnerable; Contact your support | |\n| 12.4XV | organization per the instructions in | |\n| | Obtaining Fixed Software section of | |\n| | this advisory | |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XW | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XY | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XZ | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| | | 12.4(15)T10 |\n| | | |\n| | | 12.4(20)T4 |\n| | | |\n| 12.4YA | Vulnerable; first fixed in 12.4T | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; |\n| | | Available on |\n| | | 23-OCT-2009 |\n|------------+---------------------------------------+--------------|\n| 12.4YB | 12.4(22)YB1 | 12.4(22)YB4 |\n|------------+---------------------------------------+--------------|\n| 12.4YD | Not Vulnerable | |\n|------------+---------------------------------------+--------------|\n| 12.4YE | Not Vulnerable | |\n+-------------------------------------------------------------------+\n\nNote: No Cisco IOS-XE or Cisco IOS Software Modularity releases are\naffected by this vulnerability. \n\nWorkarounds\n===========\n\nIf the affected Cisco IOS device requires SIP for VoIP services, SIP\ncannot be disabled, and therefore, no workarounds are available. \nUsers are advised to apply mitigation techniques to help limit\nexposure to the vulnerability. Mitigation consists of allowing only\nlegitimate devices to connect to the routers. To increase\neffectiveness, the mitigation must be coupled with anti-spoofing\nmeasures on the network edge. This action is required because SIP can\nuse UDP as the transport protocol. \nSome versions of Cisco IOS Software allow administrators to\naccomplish this with the following commands:\n\n sip-ua\n no transport udp\n no transport tcp\n no transport tcp tls\n\nWarning: When applying this workaround to devices that are\nprocessing Media Gateway Control Protocol (MGCP) or H.323 calls, the\ndevice will not stop SIP processing while active calls are being\nprocessed. Under these circumstances, this workaround should be\nimplemented during a maintenance window when active calls can be\nbriefly stopped. \n\nThe \"show udp connections\", \"show tcp brief all\", and \"show processes |\ninclude SIP\" commands can be used to confirm that the SIP UDP and TCP\nports are closed after applying this workaround. \n\nDepending on the Cisco IOS Software version in use, the output of\n\"show ip sockets\" still showed UDP port 5060 open, but sending\nsomething to that port caused the SIP process to emit the following\nmessage:\n\n *Feb 2 11:36:47.691: sip_udp_sock_process_read: SIP UDP Listener is\n DISABLED \n\nControl Plane Policing\n+---------------------\n\nFor devices that need to offer SIP services it is possible to use\nControl Plane Policing (CoPP) to block SIP traffic to the device from\nuntrusted sources. CoPP may be configured on a\ndevice to protect the management and control planes to minimize the\nrisk and effectiveness of direct infrastructure attacks by explicitly\npermitting only authorized traffic sent to infrastructure devices in\naccordance with existing security policies and configurations. The\nfollowing example can be adapted to the network\n\n \n !-- The 192.168.1.0/24 network and the 172.16.1.1 host are trusted. \n !-- Everything else is not trusted. The following access list is used\n !-- to determine what traffic needs to be dropped by a control plane\n !-- policy (the CoPP feature.) If the access list matches (permit)\n !-- then traffic will be dropped and if the access list does not\n !-- match (deny) then traffic will be processed by the router. \n \n \n access-list 100 deny udp 192.168.1.0 0.0.0.255 any eq 5060\n access-list 100 deny tcp 192.168.1.0 0.0.0.255 any eq 5060\n access-list 100 deny tcp 192.168.1.0 0.0.0.255 any eq 5061\n access-list 100 deny udp host 172.16.1.1 any eq 5060\n access-list 100 deny tcp host 172.16.1.1 any eq 5060\n access-list 100 deny tcp host 172.16.1.1 any eq 5061\n access-list 100 permit udp any any eq 5060\n access-list 100 permit tcp any any eq 5060\n access-list 100 permit tcp any any eq 5061\n \n \n !-- Permit (Police or Drop)/Deny (Allow) all other Layer3 and Layer4\n !-- traffic in accordance with existing security policies and\n !-- configurations for traffic that is authorized to be sent\n !-- to infrastructure devices. \n !-- Create a Class-Map for traffic to be policed by\n !-- the CoPP feature. \n \n \n class-map match-all drop-sip-class\n match access-group 100\n \n \n !-- Create a Policy-Map that will be applied to the\n !-- Control-Plane of the device. \n \n \n policy-map drop-sip-traffic\n class drop-sip-class\n drop\n \n \n !-- Apply the Policy-Map to the Control-Plane of the\n !-- device. \n \n \n control-plane\n service-policy input drop-sip-traffic\n\nWarning: Because SIP can use UDP as a transport protocol, it\nis possible to easily spoof the IP address of the sender, which may\ndefeat access control lists that permit communication to these ports\nfrom trusted IP addresses. \n\nIn the above CoPP example, the access control entries (ACEs) that\nmatch the potential exploit packets with the \"permit\" action result\nin these packets being discarded by the policy-map \"drop\" function,\nwhile packets that match the \"deny\" action (not shown) are not\naffected by the policy-map drop function. Additional information on\nthe configuration and use of the CoPP feature can be found at:\n\nhttp://www.cisco.com/web/about/security/intelligence/coppwp_gs.html\n\nand\n\nhttp://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gtrtlimt.html\n\nObtaining Fixed Software\n========================\n\nCisco has released free software updates that address these\nvulnerabilities. Prior to deploying software, customers should\nconsult their maintenance provider or check the software for feature\nset compatibility and known issues specific to their environment. \n\nCustomers may only install and expect support for the feature sets\nthey have purchased. By installing, downloading, accessing or\notherwise using such software upgrades, customers agree to be bound\nby the terms of Cisco\u0027s software license terms found at:\n\nhttp://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html\n\nor as otherwise set forth at Cisco.com Downloads at:\n\nhttp://www.cisco.com/public/sw-center/sw-usingswc.shtml\n\nDo not contact psirt@cisco.com or security-alert@cisco.com for\nsoftware upgrades. \n\nCustomers with Service Contracts\n+-------------------------------\n\nCustomers with contracts should obtain upgraded software through\ntheir regular update channels. For most customers, this means that\nupgrades should be obtained through the Software Center on Cisco\u0027s\nworldwide website at http://www.cisco.com. \n\nCustomers using Third Party Support Organizations\n+------------------------------------------------\n\nCustomers whose Cisco products are provided or maintained through\nprior or existing agreements with third-party support organizations,\nsuch as Cisco Partners, authorized resellers, or service providers\nshould contact that support organization for guidance and assistance\nwith the appropriate course of action in regards to this advisory. \n\nThe effectiveness of any workaround or fix is dependent on specific\ncustomer situations, such as product mix, network topology, traffic\nbehavior, and organizational mission. Due to the variety of affected\nproducts and releases, customers should consult with their service\nprovider or support organization to ensure any applied workaround or\nfix is the most appropriate for use in the intended network before it\nis deployed. \n\nCustomers without Service Contracts\n+----------------------------------\n\nCustomers who purchase direct from Cisco but do not hold a Cisco\nservice contract, and customers who purchase through third-party\nvendors but are unsuccessful in obtaining fixed software through\ntheir point of sale should acquire upgrades by contacting the Cisco\nTechnical Assistance Center (TAC). TAC contacts are as follows. \n\n * +1 800 553 2447 (toll free from within North America)\n * +1 408 526 7209 (toll call from anywhere in the world)\n * e-mail: tac@cisco.com\n\nCustomers should have their product serial number available and be\nprepared to give the URL of this notice as evidence of entitlement to\na free upgrade. Free upgrades for non-contract customers must be\nrequested through the TAC. \n\nRefer to:\n\nhttp://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html\n\nfor additional TAC contact information, including localized telephone\nnumbers, and instructions and e-mail addresses for use in various\nlanguages. \n\nExploitation and Public Announcements\n=====================================\n\nThe Cisco PSIRT is not aware of any public announcements or malicious\nuse of the vulnerability described in this advisory. \n\nThis vulnerability was discovered during internal testing. \n\nStatus of this Notice: FINAL\n============================\n\nTHIS DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS AND DOES NOT IMPLY ANY\nKIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF\nMERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE\nINFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS\nAT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS\nDOCUMENT AT ANY TIME. \n\nA stand-alone copy or Paraphrase of the text of this document that\nomits the distribution URL in the following section is an\nuncontrolled copy, and may lack important information or contain\nfactual errors. \n\nDistribution\n============\n\nThis advisory is posted on Cisco\u0027s worldwide website at:\n\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml\n\nIn addition to worldwide web posting, a text version of this notice\nis clear-signed with the Cisco PSIRT PGP key and is posted to the\nfollowing e-mail and Usenet news recipients. \n\n * cust-security-announce@cisco.com\n * first-bulletins@lists.first.org\n * bugtraq@securityfocus.com\n * vulnwatch@vulnwatch.org\n * cisco@spot.colorado.edu\n * cisco-nsp@puck.nether.net\n * full-disclosure@lists.grok.org.uk\n * comp.dcom.sys.cisco@newsgate.cisco.com\n\nFuture updates of this advisory, if any, will be placed on Cisco\u0027s\nworldwide website, but may or may not be actively announced on\nmailing lists or newsgroups. Users concerned about this problem are\nencouraged to check the above URL for any updates. \n\nRevision History\n================\n\n+----------------------------------------+\n| Revision | | Initial |\n| 1.0 | 2009-September-23 | public |\n| | | release |\n+----------------------------------------+\n\nCisco Security Procedures\n=========================\n\nComplete information on reporting security vulnerabilities in Cisco\nproducts, obtaining assistance with security incidents, and\nregistering to receive security information from Cisco, is available\non Cisco\u0027s worldwide website at:\n\nhttp://www.cisco.com/en/US/products/products_security_vulnerability_policy.html\n\nThis includes instructions for press inquiries regarding Cisco security\nnotices. All Cisco security advisories are available at:\n\nhttp://www.cisco.com/go/psirt\n-----BEGIN PGP SIGNATURE-----\n\niD8DBQFKukGZ86n/Gc8U/uARAh54AJ4jQJCLVMauxJXj00WMu822+kH1TQCfTzA6\n2++Xtx6BvyycWfoy75Zjtx0=\n=nUyE\n-----END PGP SIGNATURE-----\n\n. ----------------------------------------------------------------------\n\nDo you have VARM strategy implemented?\n\n(Vulnerability Assessment Remediation Management) \n\nIf not, then implement it through the most reliable vulnerability\nintelligence source on the market. \n\nImplement it through Secunia. This can be exploited to cause a buffer overflow via\nspecially crafted HTTP requests. \n\nSuccessful exploitation may allow execution of arbitrary code. \n\n2) An error in the IKE implementation can be exploited to allocate\nall available Phase 1 SAs and prevent new IPSec sessions from being\nestablished. \n\nSuccessful exploitation requires that the IKE certificate based\nauthentication method is used. \n\n3) Multiple errors exist in the IP tunnelling implementation when\nswitching network packets. These can be exploited to trigger a device\nreload via specially crafted packets. \n\nSuccessful exploitation requires that the device is configured for\nPPTP, GRE, IPinIP, Generic Packet Tunneling in IPv6, or IPv6 over IP\ntunnels, and Cisco Express Forwarding. \n\n4) An error in the implementation of the Object Groups for ACLs\nfeature can be exploited to bypass access control policies. \n\n5) An error in the H.323 implementation can be exploited to trigger a\ndevice reload via specially crafted TCP packets. \n\nSuccessful exploitation requires that H.323 is enabled (disabled by\ndefault). \n\nFor more information:\nSA36836\n\n7) An error in the SSLVPN, SSH, and IKE Encrypted Nonces features can\nbe exploited to reload a device via specially crafted packets sent to\nTCP ports 22 (for SSH) or 443 (for SSLVPN), or UDP ports 500 and 4500\n(for IKE Encrypted Nonces). \n\n8) A race condition error exists in the Authentication Proxy for\nHTTP(S), Web Authentication, and consent features. This can be\nexploited to bypass the authentication proxy services and the consent\naccept web page if a successfully authenticated session or accepted\nconsent session exists. This can be exploited to reload a device via a\nspecially crafted SIP transit packet. \n\n10) An error exists in the NTPv4 implementation while creating NTP\nreply packets. This can be exploited to trigger a device reload via a\nspecially crafted NTP packet. \n\nSOLUTION:\nUpdate to a fixed version (please see the vendor\u0027s advisories for\ndetails). \n\nPROVIDED AND/OR DISCOVERED BY:\n1, 3-10) Reported by the vendor. \n2) Reported to the vendor by a customer. \n\nORIGINAL ADVISORY:\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-h323.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-ios-fw.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-ntp.shtml\n\nOTHER REFERENCES:\nSA36836:\nhttp://secunia.com/advisories/36836/\n\n----------------------------------------------------------------------\n\nAbout:\nThis Advisory was delivered by Secunia as a free service to help\neverybody keeping their systems up to date against the latest\nvulnerabilities. \n\nSubscribe:\nhttp://secunia.com/advisories/secunia_security_advisories/\n\nDefinitions: (Criticality, Where etc.)\nhttp://secunia.com/advisories/about_secunia_advisories/\n\n\nPlease Note:\nSecunia recommends that you verify all advisories you receive by\nclicking the link. \nSecunia NEVER sends attached files with advisories. \nSecunia does not advise people to install third party patches, only\nuse those supplied by the vendor. \n\n----------------------------------------------------------------------\n\nUnsubscribe: Secunia Security Advisories\nhttp://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org\n\n----------------------------------------------------------------------\n\n\n",
"sources": [
{
"db": "NVD",
"id": "CVE-2009-2870"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002160"
},
{
"db": "BID",
"id": "36499"
},
{
"db": "VULHUB",
"id": "VHN-40316"
},
{
"db": "PACKETSTORM",
"id": "81598"
},
{
"db": "PACKETSTORM",
"id": "81635"
}
],
"trust": 2.16
},
"exploit_availability": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/exploit_availability#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"reference": "https://www.scap.org.cn/vuln/vhn-40316",
"trust": 0.1,
"type": "unknown"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40316"
}
]
},
"external_ids": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/external_ids#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"db": "NVD",
"id": "CVE-2009-2870",
"trust": 2.9
},
{
"db": "VUPEN",
"id": "ADV-2009-2759",
"trust": 2.5
},
{
"db": "SECTRACK",
"id": "1022930",
"trust": 2.5
},
{
"db": "BID",
"id": "36499",
"trust": 1.2
},
{
"db": "SECUNIA",
"id": "36835",
"trust": 0.9
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002160",
"trust": 0.8
},
{
"db": "CNNVD",
"id": "CNNVD-200910-024",
"trust": 0.7
},
{
"db": "CISCO",
"id": "20090923 CISCO IOS SOFTWARE SESSION INITIATION PROTOCOL DENIAL OF SERVICE VULNERABILITY",
"trust": 0.6
},
{
"db": "PACKETSTORM",
"id": "81598",
"trust": 0.2
},
{
"db": "VULHUB",
"id": "VHN-40316",
"trust": 0.1
},
{
"db": "PACKETSTORM",
"id": "81635",
"trust": 0.1
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40316"
},
{
"db": "BID",
"id": "36499"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002160"
},
{
"db": "PACKETSTORM",
"id": "81598"
},
{
"db": "PACKETSTORM",
"id": "81635"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
},
{
"db": "NVD",
"id": "CVE-2009-2870"
}
]
},
"id": "VAR-200909-0387",
"iot": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": true,
"sources": [
{
"db": "VULHUB",
"id": "VHN-40316"
}
],
"trust": 0.01
},
"last_update_date": "2025-04-10T22:06:02.768000Z",
"patch": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/patch#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"title": "cisco-amb-20090923-voice",
"trust": 0.8,
"url": "http://www.cisco.com/warp/public/707/cisco-amb-20090923-voice.shtml"
},
{
"title": "cisco-sa-20090923-sip ",
"trust": 0.8,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml"
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002160"
}
]
},
"problemtype_data": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"problemtype": "NVD-CWE-noinfo",
"trust": 1.0
}
],
"sources": [
{
"db": "NVD",
"id": "CVE-2009-2870"
}
]
},
"references": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/references#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"trust": 2.5,
"url": "http://www.securitytracker.com/id?1022930"
},
{
"trust": 2.5,
"url": "http://www.vupen.com/english/advisories/2009/2759"
},
{
"trust": 1.7,
"url": "http://www.cisco.com/en/us/products/products_security_advisory09186a0080af811b.shtml"
},
{
"trust": 1.7,
"url": "http://tools.cisco.com/security/center/viewalert.x?alertid=18891"
},
{
"trust": 0.8,
"url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-2870"
},
{
"trust": 0.8,
"url": "http://web.nvd.nist.gov/view/vuln/detail?vulnid=cve-2009-2870"
},
{
"trust": 0.8,
"url": "http://secunia.com/advisories/36835"
},
{
"trust": 0.8,
"url": "http://www.securityfocus.com/bid/36499"
},
{
"trust": 0.5,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml"
},
{
"trust": 0.4,
"url": "http://www.cisco.com/warp/public/707/cisco-amb-20090923-voice.shtml"
},
{
"trust": 0.3,
"url": "http://www.cisco.com/en/us/products/sw/iosswrel/products_ios_cisco_ios_software_category_home.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/620/1.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/go/psirt"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/docs/ios/12_3t/12_3t4/feature/guide/gtrtlimt.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/support/tsd_cisco_worldwide_contacts.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/sw/voicesw/ps5640/index.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/products_security_vulnerability_policy.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-bundle.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/docs/general/warranty/english/eu1ken_.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/web/about/security/intelligence/cisco_erp_sep09.html"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2009-2870"
},
{
"trust": 0.1,
"url": "http://www.cisco.com."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/techsupport"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/public/sw-center/sw-usingswc.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/web/about/security/intelligence/coppwp_gs.html"
},
{
"trust": 0.1,
"url": "http://intellishield.cisco.com/security/alertmanager/cvss"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-h323.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/36836/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-ios-fw.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/secunia_security_advisories/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/business_solutions/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-ntp.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/36835/"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/about_secunia_advisories/"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40316"
},
{
"db": "BID",
"id": "36499"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002160"
},
{
"db": "PACKETSTORM",
"id": "81598"
},
{
"db": "PACKETSTORM",
"id": "81635"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
},
{
"db": "NVD",
"id": "CVE-2009-2870"
}
]
},
"sources": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#",
"data": {
"@container": "@list"
}
},
"data": [
{
"db": "VULHUB",
"id": "VHN-40316"
},
{
"db": "BID",
"id": "36499"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002160"
},
{
"db": "PACKETSTORM",
"id": "81598"
},
{
"db": "PACKETSTORM",
"id": "81635"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
},
{
"db": "NVD",
"id": "CVE-2009-2870"
}
]
},
"sources_release_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2009-09-28T00:00:00",
"db": "VULHUB",
"id": "VHN-40316"
},
{
"date": "2009-09-23T00:00:00",
"db": "BID",
"id": "36499"
},
{
"date": "2009-10-29T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2009-002160"
},
{
"date": "2009-09-24T02:48:31",
"db": "PACKETSTORM",
"id": "81598"
},
{
"date": "2009-09-25T06:09:32",
"db": "PACKETSTORM",
"id": "81635"
},
{
"date": "2009-09-28T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200910-024"
},
{
"date": "2009-09-28T19:30:01.483000",
"db": "NVD",
"id": "CVE-2009-2870"
}
]
},
"sources_update_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2009-10-01T00:00:00",
"db": "VULHUB",
"id": "VHN-40316"
},
{
"date": "2009-09-23T19:00:00",
"db": "BID",
"id": "36499"
},
{
"date": "2009-10-29T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2009-002160"
},
{
"date": "2009-10-01T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200910-024"
},
{
"date": "2025-04-09T00:30:58.490000",
"db": "NVD",
"id": "CVE-2009-2870"
}
]
},
"threat_type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/threat_type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "remote",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
}
],
"trust": 0.6
},
"title": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/title#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Cisco IOS SIP Message Denial of Service Vulnerability",
"sources": [
{
"db": "BID",
"id": "36499"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
}
],
"trust": 0.9
},
"type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "lack of information",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200910-024"
}
],
"trust": 0.6
}
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.