Summary

• Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS^® Software that could allow an unauthenticated, remote attacker to cause a reload of an affected device when SIP operation is enabled. Remote code execution may also be possible.

  Cisco has released software updates that address these vulnerabilities. For devices that must run SIP there are no workarounds; however, mitigations are available to limit exposure of the vulnerabilities.

  This advisory is posted at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20100324-sip.

  Note: The March 24, 2010, Cisco IOS Software Security Advisory bundled publication includes seven Security Advisories. All the advisories address vulnerabilities in Cisco IOS Software. Each advisory lists the releases that correct the vulnerability or vulnerabilities detailed in the advisory. The table at the following URL lists releases that correct all Cisco IOS Software vulnerabilities that have been published on March 24, 2010, or earlier:

  https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20100324-bundle

  Individual publication links are in "Cisco Event Response: Semiannual Cisco IOS Software Security Advisory Bundled Publication" at the following link:

  http://www.cisco.com/web/about/security/intelligence/Cisco_ERP_mar10.html

Affected Products

• These vulnerabilities only affect devices running Cisco IOS Software with SIP voice services enabled.

  Vulnerable Products

  Cisco devices running affected Cisco IOS Software versions that are configured to process SIP messages are affected.

  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 follows:

  dial-peer voice  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 will process 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: Because 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.

  Cisco Unified Border Element images are also affected by these vulnerabilities.

  Note: The Cisco Unified Border Element feature (previously known as the Cisco Multiservice IP-to-IP Gateway) is a special Cisco IOS Software image that runs on Cisco multiservice gateway platforms. It provides a network-to-network interface point for billing, security, call admission control, quality of service, and signaling interworking.

  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 these vulnerabilities.

  Cisco IOS XE Software and Cisco IOS XR Software are not affected by these vulnerabilities.

  No other Cisco products are currently known to be affected by these vulnerabilities.

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.

  Three vulnerabilities exist in the SIP implementation in Cisco IOS Software that may allow a remote attacker to cause a device reload, or execute arbitrary code. These vulnerabilities are triggered when the device running Cisco IOS Software processes malformed SIP messages.

  In cases where SIP is running over TCP transport, a TCP three-way handshake is necessary to exploit these vulnerabilities.

  These vulnerabilities are addressed by Cisco bug IDs CSCsz48680 ( registered customers only) , CSCsz89904 ( registered customers only) , and CSCtb93416 ( registered customers only) , and have been assigned Common Vulnerabilities and Exposures (CVE) IDs CVE-2010-0580, CVE-2010-0581, and CVE-2010-0579, respectively.

Workarounds

• If the affected Cisco IOS device requires SIP for VoIP services, SIP cannot be disabled, and no workarounds are available. Users are advised to apply mitigation techniques to help limit exposure to the vulnerabilities. Mitigation consists of allowing only legitimate devices to connect to affected devices. 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.

  Additional mitigations that can be deployed on Cisco devices within the network are available in the companion document "Cisco Applied Mitigation Bulletin: Identifying and Mitigating Exploitation of the Cisco Unified Communications Manager Express and Cisco IOS Software H.323 and Session Initiation Protocol Denial of Service Vulnerabilities", which is available at the following location: https://sec.cloudapps.cisco.com/security/center/content/CiscoAppliedMitigationBulletin/cisco-amb-20100324-voice.

  Disable SIP Listening Ports

  For devices that do not require SIP to be enabled, the simplest and most effective workaround is to disable SIP processing on the device. Some versions of Cisco IOS Software allow administrators to disable SIP 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 from the show ip sockets command may still show the SIP ports open, but sending traffic to them will cause 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. Cisco IOS Releases 12.0S, 12.2SX, 12.2S, 12.3T, 12.4, and 12.4T support the CoPP feature. CoPP may be configured on a device to protect the management and control planes to minimize the risk and effectiveness of direct infrastructure attacks by explicitly permitting only authorized traffic sent to infrastructure devices in accordance with existing security policies and configurations. The following example can be adapted to specific network configurations:

  
  !-- The 192.168.1.0/24 network and the 172.16.1.1 host are trusted.
  !-- Everything else is not trusted. The following access list is used
  !-- to determine what traffic needs to be dropped by a control plane
  !-- policy (the CoPP feature.) If the access list matches (permit)
  !-- then traffic will be dropped and if the access list does not
  !-- match (deny) then traffic will be processed by the router.
  access-list 100 deny udp 192.168.1.0 0.0.0.255 any eq 5060
  access-list 100 deny tcp 192.168.1.0 0.0.0.255 any eq 5060
  access-list 100 deny tcp 192.168.1.0 0.0.0.255 any eq 5061
  access-list 100 deny udp host 172.16.1.1 any eq 5060
  access-list 100 deny tcp host 172.16.1.1 any eq 5060
  access-list 100 deny tcp host 172.16.1.1 any eq 5061
  access-list 100 permit udp any any eq 5060
  access-list 100 permit tcp any any eq 5060
  access-list 100 permit tcp any any eq 5061
  
  
  !-- Permit (Police or Drop)/Deny (Allow) all other Layer3 and Layer4
  !-- traffic in accordance with existing security policies and
  !-- configurations for traffic that is authorized to be sent
  !-- to infrastructure devices.
  !-- Create a Class-Map for traffic to be policed by
  !-- the CoPP feature.
  class-map match-all drop-sip-class
    match access-group 100
  
  
  !-- Create a Policy-Map that will be applied to the
  !-- Control-Plane of the device.
  policy-map control-plane-policy
   class drop-sip-class
    drop
  
  
  !-- Apply the Policy-Map to the Control-Plane of the
  !-- device.
  control-plane
   service-policy input control-plane-policy

  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.

Fixed Software

• 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.

  Each row of the Cisco IOS software table (below) names a Cisco IOS release train. 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 for this Advisory" column of the table. The "First Fixed Release for all Advisories in 24 March 2010 Bundle Publication" column indicates the earliest possible releases which have fixes for all the published vulnerabilities in this Cisco IOS Security Advisory bundled publication. Cisco recommends upgrading to the latest available release where possible.

  Major Release	Availability of Repaired Releases
  Affected 12.0-Based Releases	First Fixed Release for this Advisory	First Fixed Release for all Advisories in 24 March 2010 Bundle Publication
  There are no affected 12.0 based releases
  Affected 12.1-Based Releases	First Fixed Release for this Advisory	First Fixed Release for all Advisories in 24 March 2010 Bundle Publication
  There are no affected 12.1 based releases
  Affected 12.2-Based Releases	First Fixed Release for this Advisory	First Fixed Release for all Advisories in 24 March 2010 Bundle Publication
  There are no affected 12.2 based releases
  Affected 12.3-Based Releases	First Fixed Release for this Advisory	First Fixed Release for all Advisories in 24 March 2010 Bundle Publication
  12.3	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3B	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3BC	Not Vulnerable	Vulnerable; first fixed in 12.2SCB
  12.3BW	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3EU	Not Vulnerable	Not Vulnerable
  12.3JA	Not Vulnerable	Releases prior to 12.3(11)JA5 are vulnerable, release 12.3(11)JA5 and later are not vulnerable
  12.3JEA	Not Vulnerable	Releases prior to 12.3(8)JEA4 are vulnerable, release 12.3(8)JEA4 and later are not vulnerable
  12.3JEB	Not Vulnerable	Releases prior to 12.3(8)JEB2 are vulnerable, release 12.3(8)JEB2 and later are not vulnerable
  12.3JEC	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.3JED	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.3JK	Releases up to and including 12.3(2)JK3 are not vulnerable. Releases 12.3(8)JK1 and later are not vulnerable; first fixed in 12.4	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3JL	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.3JX	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.3T	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release. Releases up to and including 12.3(4)T11 are not vulnerable.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3TPC	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.3VA	Not Vulnerable	Not Vulnerable
  12.3XA	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XB	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.3XC	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XD	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XE	Not Vulnerable	Vulnerable; first fixed in 12.4 Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XF	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.3XG	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XI	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Releases prior to 12.3(7)XI11 are vulnerable, release 12.3(7)XI11 and later are not vulnerable
  12.3XJ	Vulnerable; migrate to any release in 12.4XN	Vulnerable; first fixed in 12.4XR
  12.3XK	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XL	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XQ	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XR	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XS	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XU	Vulnerable; migrate to any release in 15.0M or a fixed 12.4T release. Releases up to and including 12.3(8)XU1 are not vulnerable.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XW	Vulnerable; migrate to any release in 12.4XN	Vulnerable; first fixed in 12.4XR
  12.3XX	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XY	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3XZ	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YA	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YD	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YF	Vulnerable; migrate to any release in 12.4XN	Vulnerable; first fixed in 12.4XR
  12.3YG	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YH	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YI	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YJ	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YK	Releases prior to 12.3(11)YK3 are vulnerable, release 12.3(11)YK3 and later are not vulnerable;	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YM	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YQ	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YS	Vulnerable; migrate to any release in 15.0M or a fixed 12.4T release. Releases up to and including 12.3(11)YS1 are not vulnerable.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YT	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YU	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.3YX	Vulnerable; migrate to any release in 12.4XN	Vulnerable; first fixed in 12.4XR
  12.3YZ	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.3ZA	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  Affected 12.4-Based Releases	First Fixed Release for this Advisory	First Fixed Release for all Advisories in 24 March 2010 Bundle Publication
  12.4	12.4(25c) 15.0(1)M1 15.0(1)M2 ; Available on 26-MAR-10	12.4(25c) 15.0(1)M1
  12.4GC	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4JA	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4JDA	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4JDC	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4JDD	Not Vulnerable	12.4(10b)JDD1
  12.4JHA	Not Vulnerable	Not Vulnerable
  12.4JK	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4JL	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4JMA	Not Vulnerable	Releases prior to 12.4(3g)JMA2 are vulnerable, release 12.4(3g)JMA2 and later are not vulnerable
  12.4JMB	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4JX	Not Vulnerable	Vulnerable; first fixed in 12.4JA
  12.4MD	12.4(24)MD Releases prior to 12.4(22)MD are not vulnerable; Releases after 12.4(22)MD1 are not vulnerable;	12.4(24)MD
  12.4MDA	12.4(22)MDA2	12.4(22)MDA2
  12.4MR	Releases prior to 12.4(9)MR are vulnerable, release 12.4(9)MR and later are not vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4SW	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4T	12.4(22)T3 12.4(24)T2	12.4(15)T12 12.4(20)T5 12.4(24)T3; Available on 26-MAR-10 12.4(22)T4
  12.4XA	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XB	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XC	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XD	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XE	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XF	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XG	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XJ	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XK	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XL	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4XM	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XN	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4XP	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4XQ	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XR	12.4(22)XR3; Vulnerable; migrate to any release in 15.0M or a fixed 12.4T release. Releases up to and including 12.4(15)XR8 are not vulnerable.	12.4(22)XR3
  12.4XT	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XV	Not Vulnerable	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4XW	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XY	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4XZ	Not Vulnerable	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4YA	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.	Vulnerable; migrate to any release in 15.0M or a fixed 12.4 release.
  12.4YB	12.4(22)YB5	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4YD	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  12.4YE	12.4(22)YE2 12.4(24)YE	12.4(22)YE2 12.4(24)YE
  12.4YG	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory	Vulnerable; Contact your support organization per the instructions in Obtaining Fixed Software section of this advisory
  Affected 15.0-Based Releases	First Fixed Release for this Advisory	First Fixed Release for all Advisories in 24 March 2010 Bundle Publication
  There are no affected 15.0 based releases
  Affected 15.1-Based Releases	First Fixed Release for this Advisory	First Fixed Release for all Advisories in 24 March 2010 Bundle Publication
  There are no affected 15.1 based releases

  Cisco IOS-XE Software

  IOS-XE Release	First Fixed Release
  2.1.x	Not Vulnerable
  2.2.x	Not Vulnerable
  2.3.x	Not Vulnerable
  2.4.x	Not Vulnerable
  2.5.x	Not Vulnerable
  2.6.x	Not Vulnerable

Exploitation and Public Announcements

• The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerabilities described in this advisory.

  The vulnerability addressed by CSCsz48680 ( registered customers only) was discovered during the resolution of customer service requests.

  The vulnerabilities addressed by CSCtb93416 ( registered customers only) and CSCsz89904 ( registered customers only) were discovered by Cisco during internal testing.

URL

• https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20100324-sip

Revision History

• Revision 1.1	2010/March-29	Updated First Fixed releases for 12.4T
  Revision 1.0	2010-March-24	Initial public release

  Show Less