Cisco Security Advisory
Click Icon to Copy Verbose Score
AV:N/AC:L/Au:N/C:N/I:N/A:C/E:F/RL:OF/RC:C
-
Cisco IOS contains multiple vulnerabilities in the Data-link Switching (DLSw) feature that may result in a reload or memory leaks when processing specially crafted UDP or IP Protocol 91 packets.
Cisco has released software updates that address these vulnerabilities. Workarounds are available to mitigate the effects of these vulnerabilities.
This advisory is posted at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20080326-dlsw.
Note: The March 26, 2008 publication includes five Security Advisories. The Advisories all affect Cisco's Internetwork Operating System (IOS). Each Advisory lists the releases that correct the vulnerability described in the Advisory, and the Advisories also detail the releases that correct the vulnerabilities in all five Advisories.
Individual publication links are listed below:
-
Cisco IOS Virtual Private Dial-up Network Denial of Service
Vulnerability
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20080326-pptp
-
Multiple DLSw Denial of Service Vulnerabilities in Cisco IOS
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20080326-dlsw
-
Cisco IOS User Datagram Protocol Delivery Issue For IPv4/IPv6
Dual-stack Routers
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20080326-IPv4IPv6
-
Vulnerability in Cisco IOS with OSPF, MPLS VPN, and Supervisor 32,
Supervisor 720, or Route Switch Processor 720
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20080326-queue
-
Cisco IOS Multicast Virtual Private Network (MVPN) Data Leak
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20080326-mvpn
-
Cisco IOS Virtual Private Dial-up Network Denial of Service
Vulnerability
-
Vulnerable Products
This security advisory applies to all Cisco products that run any version of affected Cisco IOS software configured for DLSw. Systems that contain the DLSw feature, but do not have it enabled, are not affected.
Routers enabled for DLSw contain a line in the configuration defining a local DLSw peer. This configuration can be observed by issuing the command show running-config. Systems configured for DLSw contain lines similar to the following:
dlsw local-peer
or
dlsw local-peer peer-id <IP address>
Any version of Cisco IOS prior to the versions which are listed in the Software Versions and Fixes section below is vulnerable.
To determine the version of Cisco IOS software running on a Cisco product, log in to the device and issue the show version command to display the system banner. Cisco IOS Software will identify itself as "Internetwork Operating System Software" or simply "IOS". On the next line of output, the image name will be displayed between parentheses, followed by "Version" and the IOS release name. Other Cisco devices will not have the show version command or will give different output.
The following example identifies a Cisco product running Cisco IOS Software Release 12.3(6) with an installed image name of C3640-IS-M:
Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3640-IS-M), Version 12.3(6), RELEASE SOFTWARE (fc3)
The next example shows a product running Cisco IOS Software Release 12.3(11)T3 with an image name of C3845-ADVIPSERVICESK9-M:
Cisco IOS Software, 3800 Software (C3845-ADVIPSERVICESK9-M), Version 12.3(11)T3, RELEASE SOFTWARE (fc4) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2005 by Cisco Systems, Inc.
Additional information about Cisco IOS release naming can be found at http://www.cisco.com/warp/public/620/1.html.
Products Confirmed Not Vulnerable
Cisco IOS devices that are not configured for DLSw are not vulnerable.
No other Cisco products are currently known to be affected by these vulnerabilities.
-
Data-link switching (DLSw) provides a means of transporting IBM Systems Network Architecture (SNA) and network basic input/output system (NetBIOS) traffic over an IP network. Cisco implementation of DLSw also uses UDP port 2067 and IP Protocol 91 for Fast Sequenced Transport (FST).
Multiple vulnerabilities exists in Cisco IOS when processing UDP and IP protocol 91 packets. These vulnerabilities do not affect TCP packet processing. A successful exploitation may result in a reload of the system or a memory leak on the device, leading to a denial of service (DoS) condition.
Cisco IOS devices configured for DLSw with dlsw local-peer automatically listen for IP protocol 91 packets. A Cisco IOS device that is configured for DLSw with the dlsw local-peer peer-id <IP-address> command listen for IP protocol 91 packets and UDP port 2067.
Cisco IOS devices listen to IP protocol 91 packets when DLSw is configured. However, it is only used if DLSw is configured for Fast Sequenced Transport (FST). A DLSw FST peer configuration will contain the following line:
dlsw remote-peer 0 fst <ip-address>
It is possible to disable UDP processing in DLSw with the dlsw udp-disable command. However, disabling UDP only prevents the sending of UDP packets, it does not prevent the device from receiving and processing incoming UDP packets.
These vulnerabilities are documented in Cisco Bug ID CSCsk73104 ( registered customers only) and have been assigned Common Vulnerabilities and Exposures (CVE) ID CVE-2008-1152.
-
The workaround consists of filtering UDP packets to port 2067 and IP protocol 91 packets. Filters can be applied at network boundaries to filter all IP protocol 91 packets and UDP packets to port 2067 or can be applied on individual affected devices to permit such traffic only from trusted peer IP addresses. However, since both of the protocols are connectionless, it is possible for an attacker to spoof malformed packets from legitimate peer IP addresses.
As soon as DLSw is configured, the Cisco IOS device begins listening on IP protocol 91. However, this protocol is only used if DLSw is configured for Fast Sequenced Transport (FST). A DLSw FST peer configuration will contain the following line:
dlsw remote-peer 0 fst <ip-address>
If FST is used, filtering IP protocol 91 will break the operation, so filters need to permit protocol 91 traffic from legitimate peer IP addresses.
It is possible to disable UDP processing in DLSw with the dlsw udp-disable command. However, disabling UDP only prevents the sending of UDP packets, it does not prevent the receiving and processing of incoming UDP packets. To protect a vulnerable device from malicious packets via UDP port 2067, both of the following actions must be taken:
-
Disable UDP outgoing packets with the "dlsw udp-disable" command,
AND
-
Filter UDP 2067 in the vulnerable device using infrastructure
ACL.
Additional mitigation techniques that can be deployed on Cisco devices within the network are available in the Cisco Applied Mitigation Bulletin companion document for this advisory:
Using Control Plane Policing on Affected Devices
Control Plane Policing (CoPP) can be used to block untrusted DLSw traffic to the device. Cisco IOS software 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, which uses 192.168.100.1 to represent a trusted host, can be adapted to your network. If FST is not used, protocol 91 may be completely filtered. Additionally, if UDP is disabled with the dlsw udp-disable command, UDP port 2067 may also be completely filtered.
!--- Deny DLSw traffic from trusted hosts to all IP addresses !--- configured on all interfaces of the affected device so that !--- it will be allowed by the CoPP feature access-list 111 deny udp host 192.168.100.1 any eq 2067 access-list 111 deny 91 host 192.168.100.1 any !--- Permit all other DLSw traffic sent to all IP addresses !--- configured on all interfaces of the affected device so that it !--- will be policed and dropped by the CoPP feature access-list 111 permit udp any any eq 2067 access-list 111 permit 91 any any !--- Permit (Police or Drop)/Deny (Allow) all other Layer 3 and Layer 4 !--- 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-DLSw-class match access-group 111 !--- Create a Policy-Map that will be applied to the !--- Control-Plane of the device. policy-map drop-DLSw-traffic class drop-DLSw-class drop !--- Apply the Policy-Map to the Control-Plane of the !--- device control-plane service-policy input drop-DLSw-traffic
In the above CoPP example, the access control entries (ACEs) which 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. Please note that in the Cisco IOS 12.2S and 12.0S trains the policy-map syntax is different:
policy-map drop-DLSw-traffic class drop-DLSw-class police 32000 1500 1500 conform-action drop exceed-action drop
Additional information on the configuration and use of the CoPP feature is available at http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6642/prod_white_paper0900aecd804fa16a.html and http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gtrtlimt.html.
Using Infrastructure ACLs at Network Boundary
Although it is often difficult to block traffic transiting your network, it is possible to identify traffic that should never be allowed to target your infrastructure devices and block that traffic at the border of your network. iACLs are a network security best practice and should be considered as a long-term addition to good network security as well as a workaround for this specific vulnerability. The iACL example shown below should be included as part of the deployed infrastructure access-list that will protect all devices with IP addresses in the infrastructure IP address range. If FST is not used, protocol 91 may be completely filtered. Additionally, if UDP is disabled with the dlsw udp-disable command, UDP port 2067 may also be completely filtered.
!--- Permit DLSw (UDP port 2067 and IP protocol 91) packets !--- from trusted hosts destined to infrastructure addresses. access-list 150 permit udp TRUSTED_HOSTS MASK INFRASTRUCTURE_ADDRESSES MASK eq 2067 access-list 150 permit 91 TRUSTED_HOSTS MASK INFRASTRUCTURE_ADDRESSES MASK !--- Deny DLSw (UDP port 2067 and IP protocol 91) packets from !--- all other sources destined to infrastructure addresses. access-list 150 deny udp any INFRASTRUCTURE_ADDRESSES MASK eq 2067 access-list 150 deny 91 any INFRASTRUCTURE_ADDRESSES MASK !--- Permit/deny all other Layer 3 and Layer 4 traffic in accordance !--- with existing security policies and configurations !--- Permit all other traffic to transit the device. access-list 150 permit ip any any interface serial 2/0 ip access-group 150 in
The white paper entitled "Protecting Your Core: Infrastructure Protection Access Control Lists" presents guidelines and recommended deployment techniques for infrastructure protection access lists. This white paper can be obtained at the following link:
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801a1a55.shtml
-
Disable UDP outgoing packets with the "dlsw udp-disable" command,
AND
-
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" 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 Release
Availability of Repaired Releases
Affected 12.0-Based Releases
First Fixed Release
Recommended Release
Vulnerable; first fixed in 12.3
12.3(26)
Releases prior to 12.0(8)DA3 are vulnerable, release 12.0(8)DA3 and later are not vulnerable; migrate to any release in 12.2DA
Releases prior to 12.0(7)DB are vulnerable, release 12.0(7)DB and later are not vulnerable; first fixed in 12.4
12.4(18a)
Releases prior to 12.0(7)DC are vulnerable, release 12.0(7)DC and later are not vulnerable; first fixed in 12.4
12.4(18a)
Releases prior to 12.0(17)S5 are vulnerable, release 12.0(17)S5 and later are not vulnerable;
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; contact TAC
12.0(3c)W5(8)
Vulnerable; contact TAC
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Releases prior to 12.0(2)XC2 are vulnerable, release 12.0(2)XC2 and later are not vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.1E
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Releases prior to 12.0(4)XI2 are vulnerable, release 12.0(4)XI2 and later are not vulnerable; first fixed in 12.3
12.3(26)
Releases prior to 12.0(4)XJ5 are vulnerable, release 12.0(4)XJ5 and later are not vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Not Vulnerable
Not Vulnerable
Affected 12.1-Based Releases
First Fixed Release
Recommended Release
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Releases prior to 12.1(22)AY1 are vulnerable, release 12.1(22)AY1 and later are not vulnerable;
12.1(22)EA11
Not Vulnerable
Not Vulnerable
Not Vulnerable
Releases prior to 12.1(4)DB1 are vulnerable, release 12.1(4)DB1 and later are not vulnerable; first fixed in 12.4
12.4(18a)
Releases prior to 12.1(4)DC2 are vulnerable, release 12.1(4)DC2 and later are not vulnerable; first fixed in 12.4
12.4(18a)
12.1(27b)E4
Releases prior to 12.1(11)EA1 are vulnerable, release 12.1(11)EA1 and later are not vulnerable;
12.1(22)EA11
Not Vulnerable
Vulnerable; migrate to any release in 12.2BC
12.3(23)BC1
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.1E
Not Vulnerable
Vulnerable; first fixed in 12.1E
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Releases prior to 12.1(3)XT2 are vulnerable, release 12.1(3)XT2 and later are not vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Releases prior to 12.1(5)XV1 are vulnerable, release 12.1(5)XV1 and later are not vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Releases prior to 12.1(5)YE1 are vulnerable, release 12.1(5)YE1 and later are not vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Affected 12.2-Based Releases
First Fixed Release
Recommended Release
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.4
12.4(18a)
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.4
12.4(18a)
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
Not Vulnerable
Not Vulnerable
Not Vulnerable
Releases prior to 12.2(20)EX are vulnerable, release 12.2(20)EX and later are not vulnerable; migrate to any release in 12.2SEA
12.2(40)EX1
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Vulnerable; contact TAC
Vulnerable; contact TAC
Vulnerable; contact TAC
Vulnerable; contact TAC
Vulnerable; migrate to any release in 12.2IXF
12.2(18)IXF; Available on 31-MAR-08
Not Vulnerable
Not Vulnerable
Not Vulnerable
12.2(15)MC2h
12.2(15)MC2k
12.2(25)S15
12.2(25)S15
12.2(28)SB10
12.2(31)SB9
12.2(33)SB; Available on 31-MAR-2008
12.2(31)SB11
Vulnerable; first fixed in 12.2SB; Available on 31-MAR-2008
12.2(31)SB11
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
12.2(44)SG
12.2(44)SG
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
12.2(33)SRA6
12.2(33)SRA7
12.2(33)SRB3; Available on 07-APR-2008
12.2(33)SRB3; Available on 14-APR-08
Not Vulnerable
Vulnerable; first fixed in 12.4
12.4(18a)
Releases prior to 12.2(29a)SV1 are vulnerable, release 12.2(29a)SV1 and later are not vulnerable; migrate to any release in 12.2SVA
12.2(29b)SV
Not Vulnerable
Not Vulnerable
Not Vulnerable
Releases prior to 12.2(25)SW10 are vulnerable, release 12.2(25)SW10 and later are not vulnerable;
Vulnerable; first fixed in 12.2SXF
12.2(18)SXF13
Vulnerable; first fixed in 12.2SXF
12.2(18)SXF13
Vulnerable; first fixed in 12.2SXF
12.2(18)SXF13
Vulnerable; first fixed in 12.2SXF
12.2(18)SXF13
Vulnerable; first fixed in 12.2SXF
12.2(18)SXF13
12.2(18)SXF12
12.2(18)SXF12a
12.2(18)SXF13
12.2(33)SXH1
12.2(33)SXH2
Vulnerable; first fixed in 12.2SXF
12.2(18)SXF13
Vulnerable; first fixed in 12.2S
12.2(25)S15
12.2(31)SB11
12.2(33)SRC
Vulnerable; first fixed in 12.3
12.3(26)
12.2(8)TPC10d
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
12.2(33)XN1
12.3(26)
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Releases prior to 12.2(4)YA8 are vulnerable, release 12.2(4)YA8 and later are not vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.2S
12.2(25)S15
12.2(31)SB11
12.2(33)SRC
Vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Releases prior to 12.2(8)YJ1 are vulnerable, release 12.2(8)YJ1 and later are not vulnerable; first fixed in 12.3
12.3(26)
Not Vulnerable
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.2SXF
12.2(18)SXF13
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.4
12.4(18a)
Releases prior to 12.2(11)YV1 are vulnerable, release 12.2(11)YV1 and later are not vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.2S
12.2(25)S15
12.2(31)SB11
12.2(33)SRC
Vulnerable; first fixed in 12.2SXF
12.2(18)SXF13
Vulnerable; first fixed in 12.4
12.4(18a)
Not Vulnerable
Vulnerable; contact TAC
Vulnerable; first fixed in 12.3
12.3(26)
Vulnerable; first fixed in 12.4
12.4(18a)
Not Vulnerable
Releases prior to 12.2(13)ZH6 are vulnerable, release 12.2(13)ZH6 and later are not vulnerable; first fixed in 12.4
12.2(13)ZH11
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(15)T4
12.4(18a)
Not Vulnerable
Vulnerable; first fixed in 12.2SXH
12.2(33)SXH2
12.2(18)ZY2
12.2(18)ZY2
Affected 12.3-Based Releases
First Fixed Release
Recommended Release
12.3(24)
12.3(26)
Vulnerable; first fixed in 12.4
12.4(18a)
Not Vulnerable
Vulnerable; first fixed in 12.4
12.4(18a)
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Releases prior to 12.3(8)JK1 are vulnerable, release 12.3(8)JK1 and later are not vulnerable;
12.3(8)JK1
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.4
12.4(18a)
Not Vulnerable
Vulnerable; contact TAC
12.3(2)XA7; Available on 31-MAR-2008
12.3(2)XA7; Available on 31-MAR-08
Vulnerable; first fixed in 12.4
12.4(18a)
12.3(2)XC5
12.4(15)T4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
12.3(2)XE6; Available on 31-MAR-2008
12.4(15)T4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.3YG; Available on 16-JUN-2008
12.4(15)T4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
12.3(7)XI11; Available on 18-SEP-2008
Vulnerable; first fixed in 12.3YX
12.3(14)YX11
12.4(15)T4
Vulnerable; first fixed in 12.4
12.4(18a)
Vulnerable; first fixed in 12.4
12.4(18a)
12.3(7)XR8; Available on 31-MAR-2008
12.3(7)XR8; Available on 31-MAR-08
Not Vulnerable
Vulnerable; first fixed in 12.4T
12.4(15)T4
Vulnerable; first fixed in 12.3YX
12.3(14)YX11
12.4(15)T4
Not Vulnerable
Not Vulnerable
Not Vulnerable
Vulnerable; first fixed in 12.3YX
12.3(14)YX11
12.4(15)T4
12.3(8)YG7; Available on 16-JUN-2008
12.4(15)T4
Vulnerable; first fixed in 12.4T
12.4(15)T4
Vulnerable; first fixed in 12.4T
12.4(15)T4
Vulnerable; first fixed in 12.4T
12.4(15)T4
Vulnerable; first fixed in 12.4T
12.4(15)T4
12.3(14)YM12
12.3(14)YM12
Vulnerable; first fixed in 12.4T
12.4(15)T4
12.3(11)YS3; Available on 31-MAR-2008
12.4(15)T4
Vulnerable; first fixed in 12.4T
12.4(15)T4
Vulnerable; first fixed in 12.4XB
12.3(14)YX11
12.3(14)YX11
12.3(11)YZ3
Affected 12.4-Based Releases
First Fixed Release
Recommended Release
12.4(10c)
12.4(13e)
12.4(16b)
12.4(17)
12.4(3h)
12.4(8d)
12.4(18a)
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Not Vulnerable
Vulnerable; contact TAC
12.4(15)SW
12.4(15)T2
12.4(6)T10
12.4(9)T7
12.4(15)T4
Vulnerable; first fixed in 12.4T
12.4(15)T4
12.4(2)XB6
Vulnerable; contact TAC
12.4(4)XD10
12.4(4)XD10
12.4(6)XE2
12.4(15)T4
Not Vulnerable
12.4(9)XG2
12.4(9)XG2
Vulnerable; first fixed in 12.4T
12.4(15)T4
Vulnerable; first fixed in 12.4T
12.4(15)T4
12.4(15)XL2
12.4(15)XL2
Not Vulnerable
Not Vulnerable
12.4(6)XT2
12.4(6)XT2
12.4(11)XV
Vulnerable; contact TAC
12.4(11)XW6
Not Vulnerable
A special patch for Cisco IOS Software Modularity is also available for 12.2(18)SXF11 and can be downloaded from the Cisco IOS Software Modularity Patch Navigator at https://sec.cloudapps.cisco.com/swdf/ionpn/jsp/result.jsp?s_tarballWild=mp001-p.122-18.SXF11&reqType=cWork.
-
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory.
These vulnerabilities were found internally.
-
To learn about Cisco security vulnerability disclosure policies and publications, see the Security Vulnerability Policy. This document also contains instructions for obtaining fixed software and receiving security vulnerability information from Cisco.
-
Show Less
Revision 1.5
2008-June-26
Updated Summary to remove link and verbiage.
Revision 1.4
2008-April-25
Updated link to the CVSS score of CSCsk73104.
Revision 1.3
2008-Apr-21
Added the specific link for IOS Software Modularity patch
Revision 1.2
2008-Mar-31
Replacing IOS First Fixed Table with correct table -- data visible between 3/28 and 3/31was incorrect
Revision 1.1
2008-Mar-29
Updated Software Table for 12.0S, 12.0SY, 12.0SX and 12.0SZ due to new information on advisory ID cisco-sa-20080326-IPv4IPv6, the March 26th advisory on IPv4IPv6 Dual Stack Routers.
Revision 1.0
2008-Mar-26
Initial public release
-
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 is an uncontrolled copy, and may lack important information or contain factual errors. The information in this document is intended for end-users of Cisco products.