[cisco-ttl] Yeniden: Cisco Security Advisory: Vulnerabilities in H.323 Message Processing

From: Ilker Temir (itemir_at_cisco.com)
Date: Tue Jan 13 2004 - 11:17:40 GMT

  • Next message: ozgur yilmazer: "[cisco-ttl] 7200broadband"

    Hash: SHA1

    Az once fark etmedim, mesaj forward edilirken PGP basligi otomatik
    olarak kaldirilmis.

    Bu konuda hassas olanlar icin ayni mesaji, kendi anahtarim ile
    imzalanmis olarak tekrar gonderiyorum. Advisory'nin son hali


    adresinde bulunabilir.

    Mesaj karmasasi icin kusura bakmayin,


    - -------- Original Message --------

    Cisco Security Advisory: Vulnerabilities in H.323 Message Processing

    Document ID: 47843

    Revision 1.0 - INTERIM

    For Public Release 2004 January 13 UTC 1200

    - --------------------------------------------------------------------------


    ~ Summary
    ~ Affected Products
    ~ Unaffected Products
    ~ Details
    ~ Impact
    ~ Software Versions and Fixes
    ~ Obtaining Fixed Software
    ~ Workarounds
    ~ Exploitation and Public Announcements
    ~ Status of This Notice: INTERIM
    ~ Distribution
    ~ Revision History
    ~ Cisco Security Procedures

    - --------------------------------------------------------------------------


    Multiple Cisco products contain vulnerabilities in the processing of H.323
    messages, which are typically used in Voice over Internet Protocol (VoIP)
    or multimedia applications. A test suite has been developed by the
    University of Oulu to target this protocol and identify vulnerabilities.

    Support for the H.323 protocol was introduced in Cisco IOS« Software
    Release 11.3T. Release 11.3T, and all later Cisco IOS releases are
    affected if configured for various types of voice/multimedia application
    support. Vulnerable devices include those configured as an H.323 network
    element as well as those configured for IOS Network Address Translation
    (NAT) and those configured for IOS Firewall (also known as Context-Based
    Access Control [CBAC]).

    Other Cisco voice products that do not run Cisco IOS may also be affected.

    These vulnerabilities can be exploited repeatedly to produce a denial of
    service (DoS).

    This advisory is available at

    Affected Products

    All Cisco products that run Cisco IOS software and support H.323 packet
    processing are affected. This may include devices configured for Session
    Initiation Protocol (SIP) or Media Gateway Control Protocol (MGCP), since
    support for these protocols can enable support for H.323. Cisco AS5xxx
    series platforms are vulnerable regardless of their configuration because
    of a bug that enables H.323 but does not allow the protocol to be turned

    Other affected products that do not run Cisco IOS software include:

    ~ * Cisco CallManager versions 3.0 through 3.3

    ~ * Cisco Conference Connection (CCC)

    ~ * Cisco Internet Service Node (ISN)

    ~ * Cisco BTS 10200 Softswitch

    ~ * Cisco 7905 IP Phone H.323 Software Version 1.00

    ~ * Cisco ATA 18x series products running H.323/SIP loads with versions
    ~ earlier than 2.16.1

    Note: Cisco ATA 18x series products are only vulnerable when configured
    for H.323. They are not vulnerable when configured for SIP.

    To determine the 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.0(3) with an installed image name of C2500-IS-L. The
    release train label is 12.0.

    ~ Cisco Internetwork Operating System Software IOS (TM)
    ~ 2500 Software (C2500-IS-L), Version 12.0(3), RELEASE SOFTWARE

    The following example shows a product running Cisco IOS Software Release
    12.0(2a)T1 with an image name of C2600-JS-MZ.

    ~ Cisco Internetwork Operating System Software IOS (tm)
    ~ C2600 Software (C2600-JS-MZ), Version 12.0(2a)T1, RELEASE SOFTWARE

    Additional information about Cisco IOS version naming is available at

    If you are running Cisco IOS versions 10.x, 11.1, 11.2 or earlier, you are
    not affected.

    Cisco IOS Processing of H.323 Traffic

    There are three areas where IOS can be vulnerable to malformed H.323
    packets. Please read the following sections to determine if your router is

    Note: If you choose to block H.323 traffic using an access list to prevent
    H.323 traffic from entering the router, then you are protected and need
    not bother with the details below. Please see the Workarounds section for
    more details on how to do this. Cisco recommends that customers upgrade to
    an appropriate IOS image at their earliest convenience.

    To determine if your Cisco IOS device is processing H.323 traffic and is
    possibly vulnerable, it is necessary to understand the three different
    ways that Cisco IOS software processes H.323 traffic.

    1. H.323 Endpoints

    This includes H.323 Gateway, H.323 Gatekeeper, H.323 Gatekeeper with Proxy
    and ALL of the AS5xxx platforms.

    - - From the enable prompt, run the show process cpu command and look for a
    process called CCH323_CT. In later versions of Cisco IOS software, you can
    execute the show process cpu | include CCH323_CT .

    ~ Router# show process cpu | include CCH323_CT
    ~ 112 Mwe 60F3E5E0 295112 239401 123220072/24000 0

    Note: Not all access server images support H.323. Only images with a
    "PLUS" feature set (such as IP PLUS, ENTERPRISE PLUS) support voice and
    will have the CCH323_CT process running.

    ~ * If you see the a process called CCH323_CT, your router is affected.
    ~ Please consult the IOS table to determine which version is appropriate
    ~ for your device. If you cannot immediately upgrade, the following
    ~ workarounds may work for you

    ~ + If you are not using H.323 within your network, an inbound access
    ~ list to block TCP port 1720 will protect your router, but it is
    ~ recommended that you upgrade as soon as is feasible.

    ~ + If you are using H.323, then you can configure an access list to
    ~ restrict TCP port 1720 traffic to known, trusted IP addresses.
    ~ Again, upgrading as soon as is feasible is recommended.

    ~ * If you do NOT see the CCH323_CT process, you may still be vulnerable.
    ~ Some configurations of H.323 Gatekeeper are vulnerable. Affected
    ~ configurations are those gatekeepers configured for H.323 Proxy. To
    ~ check to see if you are configured as a gatekeeper, check your
    ~ configuration for the line "proxy h323" in the global configuration.
    ~ If you have "proxy h323" configured, then you are vulnerable.

    ~ + If you are not using GK proxy functionality, you can disable proxy
    ~ functionality by doing the following configuration.

    ~ Note: This will drop all calls being managed by the gatekeeper.
    ~ Perform this only when you can safely stop gatekeeper
    ~ functionality.

    ~ Router(config)#no proxy h323
    ~ Router(config)#gatekeeper
    ~ Router(config-gk)#shutdown
    ~ Router(config-gk)#no shutdown

    ~ + If you are using H.323 proxy, your options are to either configure
    ~ an access list to restrict TCP port 1720 traffic to known, trusted
    ~ IP addresses, or to upgrade your IOS version.

    2. IOS Firewall (Context-Based Access Control)

    If your IOS device is configured to use IOS Firewall (IOS FW, or
    Context-Based Access Control [CBAC]), check to see if IOS FW is running on
    the device by issuing the show ip inspect all command. Look for the
    following lines indicating that IOS FW is applied to an interface. In this
    case, inspection rule "<NAME>" is applied inbound to interface

    ~ Interface Configuration
    ~ Interface FastEthernet0/0
    ~ Inbound inspection rule is <NAME>
    ~ tcp alert is on audit-trail is off timeout 3600
    ~ h323 alert is on audit-trail is off timeout 3600
    ~ Outgoing inspection rule is not set

    ~ * To turn off inbound IOS FW (CBAC) on interface FastEthernet0/0, enter
    ~ the following commands in interface configuration mode.

    ~ Router#config t
    ~ Router(config)#Interface FastEthernet 0/0
    ~ Router(config-if)#no ip inspect <NAME> in

    ~ * If outbound IOS FW (CBAC) is configured on FastEthernet0/0, enter the
    ~ following commands in interface configuration mode.

    ~ Router#config t
    ~ Router(config)#Interface FastEthernet 0/0
    ~ Router(config-if)#no ip inspect <NAME> out

    ~ * To turn off the IOS FW (CBAC) processing of H.323 messages only while
    ~ leaving other IOS FW behavior unaffected, enter the following command
    ~ in global configuration mode.

    ~ Router(config)#no ip inspect name <NAME> h323

    Cisco recommends that you upgrade your IOS as soon as possible.

    3. IOS Network Address Translation (NAT)

    If you have configured NAT rules and have NAT activated on any interface,
    check to see if NAT is configured and activated on the device by issuing
    the show ip nat statistics command.

    ~ Router#show ip nat statistics

    ~ Total active translations: 3 (3 static, 0 dynamic; 0 extended
    ~ Outside interfaces
    ~ Inside interfaces
    ~ Hits: 0 Misses: 0
    ~ Expired translations: 0
    ~ Dynamic mappings:

    ~ * If there is no output or the output doesn't list any inside or outside
    ~ interfaces (as in the example above), then the IOS device is not doing
    ~ NAT and you are not vulnerable because of NAT.

    ~ * If the output does list any inside or outside interfaces, then you may
    ~ be vulnerable because of NAT. An example is shown below.

    ~ Total active translations: 3 (3 static, 0 dynamic; 0 extended
    ~ Outside interfaces:
    ~ Serial3/0
    ~ Inside interfaces:
    ~ Serial1/0
    ~ Hits: 0 Misses: 0
    ~ Expired translations: 0
    ~ Dynamic mappings:

    ~ * You are not vulnerable because of NAT if your configuration only
    ~ contains Port Address Translation (PAT) statements and your PAT
    ~ statements do not explicitly specify TCP port 1720 in your PAT
    ~ translations.

    ~ + To see if you are doing only PAT, check to see if your IOS NAT
    ~ configuration contains any of the following NAT rules without the
    ~ overload, route-map, or extendable keywords.

    ~ ip nat outside source ...
    ~ ip nat inside destination ...
    ~ ip nat inside source ...

    ~ If you see any of the above lines without the overload, route-map,
    ~ or extendable keywords, then you are vulnerable.

    ~ + To see if you are doing a static PAT for H.323 (TCP port 1720),
    ~ look for any lines with the following pattern.

    ~ ip nat (inside|outside) source static tcp
    ~ ip-addr (port|1720) ip-addr (1720|port)

    ~ The following examples would be vulnerable.

    ~ ip nat inside source static tcp 1720 5834
    ~ ip nat outside source static tcp 6884 1720
    ~ ip nat inside source static tcp 1720 1720

    ~ The following examples would not be vulnerable.

    ~ ip nat inside source static tcp 53 53
    ~ ip nat outside source static udp 1720

    ~ If any of your configuration lines are vulnerable, please consult
    ~ the Workarounds section.

    To determine if a particular Cisco IOS release is vulnerable, consult the
    list below in the Software Versions and Fixes section to determine if the
    product is running an affected version of software.

    Unaffected Products

    The following list of Cisco products is provided specifically to list
    those products that customers may also be concerned about in regards to
    these vulnerabilities. The products below are not affected either because
    they are not vulnerable or because they do not support H.323 processing.
    Any other Cisco products that have not been identified as vulnerable or
    have been omitted from the list below should be considered as not
    vulnerable, as no other Cisco products are known to be affected by these

    ~ * Cisco IP Phone models 7960, 7940, 7912, 7910, 7902, 30VIP, and 12SP+

    ~ * Cisco uOne (All Versions)

    ~ * VG248 Analog Phone Gateway

    ~ * Cisco Unity Server

    ~ * Catalyst 6000 WS-X6608 Voice Services Module and WS-X6624 FXS Analog
    ~ Station Interface Module

    ~ * PGW2200, SC2200, VSC3000 and H.323 Signalling Interface (HSI)

    ~ * Cisco IP/VC 3500 Series

    ~ * IP/TV series

    ~ * Catalyst 19xx, 28xx, 290x, 292x, 2948g, 3000, 3200, 3900, 4000, 4912g,
    ~ and 5000 series switches

    ~ * Catalyst 2900XL, 2900XL-LRE, 2940, 2950, 2950-LRE, 2955, 2970, 3500XL,
    ~ 3550, and 3750 series switches

    ~ * Cache Engine series

    ~ * Content Engine series

    ~ * SN5400 series storage routers

    ~ * VPN 3000 and VPN 5000 series VPN concentrators

    ~ * Voice Interworking Service Module (VISM)

    ~ * VCO/4K

    ~ * Cisco Secure Intrusion Detection System (NetRanger) appliance and IDS
    ~ Module

    ~ * BR340, WGB340, AP340, AP350, and BR350 Cisco/Aironet wireless products

    ~ * Cisco Aironet 1100 series, 1200 series, and 1400 series wireless
    ~ products

    ~ * Cisco PIX Firewall

    ~ * Cisco Catalyst 6500 Series Firewall Services Module

    ~ * Cisco 6xx series DSL modems running CBOS

    ~ * Cisco 7xx series routers

    ~ * Cisco 12000 series routers

    ~ * Cisco 10000 series routers

    ~ * 61xx and 62xx series DSLAMs

    ~ * Cisco CSS11xxx series (including SSL Accelerator)

    ~ * LocalDirector

    ~ * BPX, IGX, MGX WAN switches, and the Service Expansion Shelf

    ~ * Cisco Intelligent Contact Management (ICM)

    ~ * Cisco ONS 15xxx platforms


    H.323 is the International Telecommunications Union (ITU) standard for
    real-time multimedia communications and conferencing over packet-based
    (IP) networks. A subset of the H.323 standard is H.225.0, a standard used
    for call signalling protocols and media stream packetization over IP

    The H.225.0 standard defines message formats for call setup, call control,
    and communications using Abstract Syntax Notation One (ASN.1). ITU
    Standard Q.931, which was developed for call signalling purposes in ISDN
    networks, is also used as the standard for the call setup messages within

    The University of Oulu Secure Programming Group (OUSPG) has created a test
    suite for H.323, more specifically the H.225.0 and Q.931 messages, to help
    support proactive discovery and resolution of vulnerabilities in the
    processing of H.323 messages. The test suite is generally used to analyze
    a protocol and produce messages that probe various design limits within an
    implementation of a protocol. Test packets containing overly long or
    exceptional elements in various fields of the H.323 Protocol Data Units
    (PDUs) can be programmatically generated and then transmitted to a network
    device under test. The PROTOS test suite for H.323, as distributed,
    contains approximately 4500 individual test cases.

    The vulnerabilities discovered in the affected products can be easily and
    repeatedly demonstrated with the use of the OUSPG PROTOS Test Suite for
    H.323. The largest group of vulnerabilities described in this advisory
    result from insufficient checking of H.225.0 messages as they are received
    and processed by an affected system. Malformed H.225.0 messages received
    by affected systems can cause various parsing and processing functions to
    fail, which may result in a system crash and reload (or reboot) in most

    Typically, H.323 network elements implement call signalling over both UDP
    and TCP transports on port 1720. The H.323 test suite from OUSPG only
    tests the TCP implementation on port 1720 by default.

    Cisco IOS

    | Cisco IOS | Description of |
    | Software | Vulnerability |
    | Release | |
    | 11.1, 11.2, | Not vulnerable |
    | 11.3, 12.3 | |
    | | Vulnerabilities exist in |
    | 11.3T, 12.0, | the processing of H.323 |
    | 12.0S,12.0T, | Network Element traffic. |
    | 12.1, 12.1T, | This includes H.323 |
    | 12.1E, 12.2, | Gateway, H323 Gatekeeper, |
    | 12.2S, 12.2T | and H.323 Gatekeeper with |
    | | Proxy. |
    | 12.1, 12.1E, | Vulnerabilities exist in |
    | 12.2, 12.2T, | the processing of H.323 |
    | 12.2S, 12.3T | IOS NAT traffic. |
    | 12.0, 12.1, | Vulnerabilities exist in |
    | 12.1E, 12.2, | the processing of H.323 |
    | 12..2T, | IOS Firewall (CBAC) |
    | 12.2S | traffic. |

    The vulnerabilities in Cisco IOS for devices acting as H.323 dial-peer
    endpoints are documented in the following Bug IDs: CSCdt09262 ( registered
    customers only) , CSCdt54401 ( registered customers only) , CSCdw14262 (
    registered customers only) , CSCdx76632 ( registered customers only) ,
    CSCdx77253 ( registered customers only) , CSCea19885 ( registered
    customers only) , CSCea32240 ( registered customers only) , CSCea36231 (
    registered customers only) , CSCea33065 ( registered customers only) ,
    CSCea42826 ( registered customers only) , CSCea42527 ( registered
    customers only) , CSCea44227 ( registered customers only) , CSCea44309 (
    registered customers only) , CSCea46342 ( registered customers only) , and
    CSCec79541 ( registered customers only) .

    For those Cisco IOS devices acting as a H.323 gatekeeper with proxy
    configured, the vulnerabilities are documented in the following Bug IDs:
    CSCea51076 ( registered customers only) , CSCea51030 ( registered
    customers only) , and CSCea54851 ( registered customers only) .

    Cisco IOS devices performing NAT translations on H.323 v3/4 traffic may be
    vulnerable. Releases based off 12.2T must be running a version of IOS that
    is based off 12.2(11)T or later and must have the hidden command ip nat
    service h323all enabled. The default condition for this command is
    disabled. In releases based off 12.1 and 12.1E, the device is only
    vulnerable to packets sent from the outside interface to the inside
    interface. This means that networks are only vulnerable if they have
    static translations configured and accept connections to port 1720. A
    dynamic translation can occur on port 1720, but the attack traffic would
    then have to return from the destination address of the original flow and
    must traverse the router while the translation is still active. Methods to
    reduce exposure for dynamic translations are listed in the Workarounds

    The vulnerabilities in Cisco IOS for devices doing NAT on H.323 packets
    starting in IOS 12.1 are documented in the following Bug IDs: CSCdr48143 (
    registered customers only) , CSCdx40184 ( registered customers only) ,
    CSCea27536 ( registered customers only) , CSCec76694 ( registered
    customers only) , and CSCed28873 ( registered customers only) .

    The vulnerabilities in Cisco IOS for devices running IOS Firewall Feature
    Set doing deep packet inspection of H.323 packets in IOS starting in 12.1
    are documented in the following Bug IDs: CSCec76776 ( registered customers
    only) and CSCec87533 ( registered customers only) .

    Cisco CallManager

    The vulnerabilities in Cisco CallManager are documented in Bug IDs
    CSCdx82831 ( registered customers only) , CSCea46545 ( registered
    customers only) , and CSCea55518 ( registered customers only) .

    In order for a Cisco CallManager running 3.1 or 3.2 to be vulnerable, the
    IP address of the originating device must be configured as a H.323
    gateway, H.323 client, or intercluster trunk on the CallManager, or "Allow
    Anonymous Calls" must be enabled in the gatekeeper section of the
    CallManager configuration. If a CallManager receives H.323 messages from a
    device that is not configured as an H.225.0 device, the TCP session will
    be closed before the H.225.0 message is processed. If "Allow Anonymous
    Calls" is enabled in the gatekeeper configuration, the CallManager server
    is vulnerable since it will try to parse the H.225.0 message from any
    originating source.

    In CallManager 3.3, the server is vulnerable and will try to parse H.225.0
    messages received from any originating source, but the CallManager may be
    listening on a port other than TCP 1720. Since the port number for
    anonymous calls is something other than TCP 1720, a potential attacker
    would need to determine which random port the CallManager H.323 gateway is
    listening on in order to carry out a successful attack.

    Cisco Conference Connection

    All versions of Cisco Conference Connection (CCC) are affected. There are
    currently no software fixes planned for Cisco Conference Connection (CCC).
    Customers running CCC should implement a workaround to limit H.323 traffic
    from trusted hosts only. A workaround for this may be found in the
    Workarounds section.

    Cisco Internet Service Node

    All versions of Internet Service Node (ISN) are affected. There are
    currently no software fixes planned for Cisco Internet Service Node (ISN).
    Customers running ISN should implement a workaround to limit H.323 traffic
    from trusted hosts only. A workaround for this may be found in the
    Workarounds section.

    Cisco 7905 Series IP Phone

    The vulnerabilities in the Cisco 7905 IP Phone are documented in Bug ID
    CSCec77152 ( registered customers only) .

    Cisco ATA18x Series Analog Telephony Devices

    The vulnerabilities in the Cisco ATA18x devices are documented in Bug IDs
    CSCea46231 ( registered customers only) and CSCea48726 ( registered
    customers only) .

    Cisco BTS 10200 Softswitch

    The vulnerabilities in the Cisco BTS 10200 Softswitch are documented in
    BugID CSCea48755 ( registered customers only) .


    The vulnerabilities may be exploited to produce a denial of service (DoS)
    attack. When the vulnerabilities are exploited, they may cause an affected
    product to crash and reload. In the case of the Cisco CallManager, ISN,
    and CCC, exploitation will result in a crash or a hang indicated by
    processor utilization of 100%. When the CPU utilization is at 100% on
    server-based platforms, call processing services degrade severely, calls
    may drop, and no new calls can be established. A reboot of the device is
    required to return it to normal service.

    Software Versions and Fixes

    Cisco IOS Software

    Each row of the table describes a release train and the platforms or
    products for which it is intended. If a given release train is vulnerable,
    then the earliest possible releases that contain the fix and the
    anticipated date of availability for each are listed in the Rebuild,
    Interim, and Maintenance columns. In some cases, no rebuild of a
    particular release is planned; this is marked with the label "Not
    scheduled." A device running any release in the given train that is
    earlier than the release in a specific column (less than the earliest
    fixed release) is known to be vulnerable, and it should be upgraded at
    least to the indicated release or a later version (greater than the
    earliest fixed release label).

    When selecting a release, keep in mind the following definitions.

    ~ * Maintenance

    ~ Most heavily tested and highly recommended release of any label in a
    ~ given row of the table.

    ~ * Rebuild

    ~ Constructed from the previous maintenance or major release in the same
    ~ train, it contains the fix for a specific vulnerability. Although it
    ~ receives less testing, it contains only the minimal changes necessary
    ~ to effect the repair. Cisco has made available several rebuilds of
    ~ mainline trains to address this vulnerability, but strongly recommends
    ~ running only the latest maintenance release on mainline trains.

    ~ * Interim

    ~ Built at regular intervals between maintenance releases and receives
    ~ less testing. Interims should be selected only if there is no other
    ~ suitable release that addresses the vulnerability, and interim images
    ~ should be upgraded to the next available maintenance release as soon
    ~ as possible. Interim releases are not available through manufacturing,
    ~ and usually they are not available for customer download from CCO
    ~ without prior arrangement with the Cisco Technical Assistance Center
    ~ (TAC).

    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 TAC for
    assistance, as shown in the section following this table.

    Note: For the purposes of the table below, the identifier "Element"
    covers the fixes for IOS devices running as H.323 endpoints and as
    gatekeepers with proxy configured.

    | Train | Vulnerable | Availability of Fixed Releases |
    | | Configuration | |
    | 10.x-based Releases | Not Vulnerable |
    | 11.x-based Releases | Rebuild | Interim | Maintenance |
    | 11.0 | | Not Vulnerable |
    | 11.1 | | Not Vulnerable |
    | 11.1AA | | Not Vulnerable |
    | 11.1CA | | Not Vulnerable |
    | 11.1CC | | Not Vulnerable |
    | 11.2 | | Not Vulnerable |
    | 11.2P | | Not Vulnerable |
    | 11.2SA | | Not Vulnerable |
    | 11.3 | | Not Vulnerable |
    | | | Introduced H.323 feature in 11.3(3)T |
    | | | |
    | | | Vulnerable |
    | 11.3T | | |
    | | | No Software Fixes Scheduled |
    | | | |
    | | | Migrate to 12.0 |
    | 12.0-based Releases | Rebuild | Interim | Maintenance |
    | | | | | 12.0(28) |
    | | Element | | | |
    | | | | | available |
    | | | | | 15-Jan-2004 |
    | |---------------+-------------+-----------+--------------|
    | 12.0 | | | | 12.0(28) |
    | | NAT | | | |
    | | | | | available |
    | | | | | 15-Jan-2004 |
    | |---------------+----------------------------------------|
    | | IPFW | Not Vulnerable |
    | 12.0D | | Not Vulnerable |
    | 12.0DA | | Not Vulnerable |
    | 12.0DC | | Not Vulnerable |
    | | | 2600/3600 | | |
    | | | Platforms | | |
    | | | ONLY | | 2600/3600 |
    | | | | | Platforms |
    | | Element | 12.0(25)S1, | | ONLY |
    | | | | | |
    | 12.0S | | 12.0(24)S2, | | 12.0(26)S |
    | | | | | |
    | | | 12.0(23)S3 | | |
    | |---------------+----------------------------------------|
    | | NAT | Not Vulnerable |
    | |---------------+----------------------------------------|
    | | IPFW | Not Vulnerable |
    | 12.0SC | | Not Vulnerable |
    | 12.0SL | | Not Vulnerable |
    | 12.0SP | | Not Vulnerable |
    | 12.0ST | | No fixes planned, only 2600/3600 |
    | | | platforms vulnerable |
    | 12.0SX | | Not Vulnerable |
    | 12.0SY | | Not Vulnerable |
    | 12.0SZ | | Not Vulnerable |
    | 12.0T | | Vulnerable. No fixes planned. |
    | 12.0W5 | | Not Vulnerable |
    | 12.0WC | | Not Vulnerable |
    | 12.0WT | | Not Vulnerable |
    | 12.0XC | | Vulnerable. Migrate to 12.1(21) |
    | 12.0XD | | Vulnerable. Migrate to 12.1(21) |
    | 12.0XG | | Vulnerable. Migrate to 12.1(21) |
    | 12.0XH | | Vulnerable. Migrate to 12.1(21) |
    | 12.0XI | | Vulnerable. Migrate to 12.1(21) |

    Bu listenin Cisco Systems ile dogrudan herhangi bir baglantisi bulunmamaktadir.

    Listeden cikmak išin cisco-ttl-unsubscribe_at_yahoogroups.com adresine bir e-posta g÷nderebilirsiniz.

    ------------------------ Yahoo! Groups Sponsor ---------------------~-->
    Upgrade to 128-bit SSL Security!

    Yahoo! Groups Links

    To visit your group on the web, go to:

    To unsubscribe from this group, send an email to:

    Your use of Yahoo! Groups is subject to:

    This archive was generated by hypermail 2.1.5 : Tue Jan 13 2004 - 15:19:34 GMT