- NANOG - lists.nanog.org

Re: Cable-Tying with Waxed Twine
by Richard Naylor 25 Jan '07

25 Jan '07

Confession time - I'm over 50 At 09:41 p.m. 24/01/2007 -0700, you wrote: >As for plastic ties (TyRap is the brand name for the Thomas & Betts version) >they may be easy to use, but they do have several functional drawbacks, >including: > >1) difficulty in maintaining consistent tension from tie to tie, and as > a correlary it is comparatively easy to overtighten one, risking > compression-related damage to the underlying cabling, or as mentioned > above, > increasing crosstalk when using twisted-pair cables You can buy a cable-tie gun from Panduit, along with ties on a bandolier. They are used in appliance manufacture for making up wiring looms, instead of lacing them. The tension is programmable .You may also remember that in cars, the wiring harness was in a cloth jacket...... >2) can harden and/or become brittle over time, eventually failing under stress H'mm - you buy various grades of cable-tie. I have a lot of personal experience with a black Ty-Rap. Its black with a stainless-steel tag. The black makes it UV-stable and I get nervous if we don't have a few thousand in stock. I carry a few hundred in my van... White ties aren't UV stable and so are indoor rated only. Of course I live in a country where the weather report gives a UV rating each day, due to the Ozone depletion making a hole right above us - due to CFCs in aerosol can's. Thanks guys....and girls. Get Joe Abley to tell you about CityLink over a few beers. But basically, its a 20Km metro fiber network suspended off the trolley bus wires. I built the fist 200 odd buildings, before we got "staff". The fiber is attached to a synthetic rope (kevlar) which is the catenary wire, by a TyRap ty25 (from memory), every 300 mm. The way we work was my van pulled the trailer with the fiber drum, Ryan and Glenn were in the cherry-picker, moving from pole to pole. I was on the ground cable tying like mad. Ryan then pulled the cable up, tensioned it, made it fast,and we moved on. Been doing it since 1996. These days we use self supporting fiber, so run much faster, no cable ties until we overlay.... >3) typical background vibration causes them to tend to chafe the sheaths >of the > wiring that the ties are in direct contact with, over a period of years. buy the ones with stainless tags - they last for years. The cheap plastic ones are toys >Lacing is a lot slower than using platic ties, and doing it is rough on your >fingers. If you're lucky you know a data tech who can show you how to do it >properly, it's really not something that you can just describe in writing. > >Depending upon the specific need, contact points may also have pieces of fish >paper laced to them before the wiring is laid out and laced into place. >Not unusual to see this when DC power cables are being secured. H'mmm - the DC cables I'm used to are the size of your arm - per polarity.....we don't lace them, just bury them. But sorry - I'm old and been around. I worked in a power utility for 14 years. BTW Broadband over Power - we call ripple control. It turns on the street lights, load control etc. Been doing it for years and its not hard to go both ways. Zellweger in Uster Switzerland used to make the cool stuff. I have photos somewhere..... We also inject DC into the AC network, but thats another beer or two. First you have to work out why the utilities use AC...... Rich

1 0

NANOG 39: Partial agenda posted
by Steve Feldman 24 Jan '07

24 Jan '07

The agenda for the plenary sessions at NANOG 39 has been posted at http://nanog.org/mtg-0702/topics.html Times for the tutorial and BOF sessions, which will be held Monday and Tuesday afternoons, will be updated soon. See you in Toronto! (U.S. residents: don't forget your passports...) Steve Feldman PC Chair

1 0

New APNIC IPv4 address ranges
by Leslie Nobile 24 Jan '07

24 Jan '07

Forwarding on for APNIC... -------- Original Message -------- Subject: [Apnic-announce] New APNIC IPv4 address ranges Date: Thu, 18 Jan 2007 16:00:03 +1000 From: helpdesk(a)apnic.net Reply-To: apnic-talk(a)apnic.net To: apnic-announce(a)apnic.net Dear colleagues APNIC received the following IPv4 address blocks from IANA in Jan 2007 and will be making allocations from these ranges in the near future: 116/8 APNIC 117/8 APNIC 118/8 APNIC 119/8 APNIC 120/8 APNIC APNIC has made this announcement to enable the Internet community to update network configurations, such as routing filters, where required. Routability testing of new prefixes will commence on Friday January 19 2007. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon/debogon.html For more information on the resources administered by APNIC, please see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, please see: http://www.apnic.net/db/min-alloc.html Kind regards Guangliang ________________________________________________________________ Guangliang Pan email: helpdesk(a)apnic.net Resources Services Manager sip: helpdesk(a)voip.apnic.net APNIC phone: +61 7 3858 3188 http://www.apnic.net/ fax: +61 7 3858 3199 ________________________________________________________________

1 0

Re: Colocation in the US.
by Tony Varriale 24 Jan '07

24 Jan '07

The current high watt cooling technologies are definately more expensive (much more). Also, a facility would still need traditional forced to maintain the building climate. tv ----- Original Message ----- From: "Todd Glassey" <tglassey(a)earthlink.net> To: "Tony Varriale" <tvarriale(a)comcast.net>; <nanog(a)merit.edu> Sent: Wednesday, January 24, 2007 2:09 PM Subject: Re: Colocation in the US. > If the cooling is cheaper than the cost of the A/C or provides a backup, > its a no brainer. > > Todd Glassey > > > -----Original Message----- >>From: Tony Varriale <tvarriale(a)comcast.net> >>Sent: Jan 24, 2007 11:20 AM >>To: nanog(a)merit.edu >>Subject: Re: Colocation in the US. >> >> >>I think the better questions are: when will customers be willing to pay >>for >>it? and how much? :) >> >>tv >>----- Original Message ----- >>From: "Mike Lyon" <mike.lyon(a)gmail.com> >>To: "Paul Vixie" <vixie(a)vix.com> >>Cc: <nanog(a)merit.edu> >>Sent: Wednesday, January 24, 2007 11:54 AM >>Subject: Re: Colocation in the US. >> >> >>> >>> Paul brings up a good point. How long before we call a colo provider >>> to provision a rack, power, bandwidth and a to/from connection in each >>> rack to their water cooler on the roof? >>> >>> -Mike >>> >>> On 24 Jan 2007 17:37:27 +0000, Paul Vixie <vixie(a)vix.com> wrote: >>>> >>>> drais(a)atlasta.net (david raistrick) writes: >>>> >>>> > > I had a data center tour on Sunday where they said that the way >>>> > > they >>>> > > provide space is by power requirements. You state your power >>>> > > requirements, they give you enough rack/cabinet space to *properly* >>>> > > house gear that consumers that >>>> > >>>> > "properly" is open for debate here. ... It's possible to have a >>>> > facility built to properly power and cool 10kW+ per rack. Just that >>>> > most >>>> > colo facilties aren't built to that level. >>>> >>>> i'm spec'ing datacenter space at the moment, so this is topical. at >>>> 10kW/R >>>> you'd either cool ~333W/SF at ~30sf/R, or you'd dramatically increase >>>> sf/R >>>> by requiring a lot of aisleway around every set of racks (~200sf per 4R >>>> cage) to get it down to 200W/SF, or you'd compromise on W/R. i suspect >>>> that the folks offering 10kW/R are making it up elsewhere, like 50sf/R >>>> averaged over their facility. (this makes for a nice-sounding W/R >>>> number.) >>>> i know how to cool 200W/SF but i do not know how to cool 333W/SF unless >>>> everything in the rack is liquid cooled or unless the forced air is >>>> bottom->top and the cabinet is completely enclosed and the doors are >>>> never >>>> opened while the power is on. >>>> >>>> you can pay over here, or you can pay over there, but TANSTAAFL. for >>>> my >>>> own purposes, this means averaging ~6kW/R with some hotter and some >>>> colder, and cooling at ~200W/SF (which is ~30SF/R). the thing that's >>>> burning me right now is that for every watt i deliver, i've got to burn >>>> a >>>> watt in the mechanical to cool it all. i still want the rackmount >>>> server/router/switch industry to move to liquid which is about 70% more >>>> efficient (in the mechanical) than air as a cooling medium. >>>> >>>> > > It's a good way of looking at the problem, since the flipside of >>>> > > power >>>> > > consumption is the cooling problem. Too many servers packed in a >>>> > > small >>>> > > space (rack or cabinet) becomes a big cooling problem. >>>> > >>>> > Problem yes, but one that is capable of being engineered around >>>> > (who'd >>>> > have ever though we could get 1000Mb/s through cat5, after all!) >>>> >>>> i think we're going to see a more Feinman-like circuit design where >>>> we're >>>> not dumping electrons every time we change states, and before that >>>> we'll >>>> see a standardized gozinta/gozoutta liquid cooling hookup for rackmount >>>> equipment, and before that we're already seeing Intel and AMD in a >>>> watts-per-computron race. all of that would happen before we'd >>>> air-cool >>>> more than 200W/SF in the average datacenter, unless Eneco's chip works >>>> out >>>> in which case all bets are off in a whole lotta ways. >>>> -- >>>> Paul Vixie >>>> >> >

1 0

IAB Workshop on Routing and Addressing [Was: Re: Google wants to be yo ur Internet]
by Fergie 24 Jan '07

24 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -- Jason LeBlanc <jml(a)packetpimp.org> wrote: >...Some days it kills me that v6 >is still not really viable, I keep asking providers where they're >at with it. Their most common complaint is that the operating >systems don't support it yet. They mention primarily Windows since >that is what is most implemented, not in the colo world but what the >users have. I suggested they offer a service that somehow translates >(heh, shifting the pain to them) v4 to v6 for their customers to move >it along. > If you *really* want to know where things with IPv6, then you need to read this: Report from the IAB Workshop on Routing and Addressing http://www.ietf.org/internet-drafts/draft-iab-raws-report-00.txt - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.5.2 (Build 4075) wj8DBQFFt5xMq1pz9mNUZTMRApvtAKCSIwmfi4ISc8jFg7yHgt2rlrK+7gCgyHiY /ukrrvZTVFL52zm7eu2ZuZs= =OtBi -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(at)netzero.net ferg's tech blog: http://fergdawg.blogspot.com/

1 0

Super Bowl Sunday February 4th
by Ron Muir 24 Jan '07

24 Jan '07

Is there anything organized for the Super Bowl on Sunday Night? The last time Super Bowl fell on a NANOG (NANOG 15) Sunday several of the sponsors got together and had a Super Bowl party at the hotel. Does anyone know of anything this time? Ron Muir

2 1

Cisco Security Advisory: IPv6 Routing Header Vulnerability
by Cisco Systems Product Security Incident Response Team 24 Jan '07

24 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cisco Security Advisory: IPv6 Routing Header Vulnerability Advisory ID: cisco-sa-20070124-IOS-IPv6 http://www.cisco.com/warp/public/707/cisco-sa-20070124-IOS-IPv6.shtml Revision 1.0 For Public Release 2007 January 24 1600 UTC (GMT) - ----------------------------------------------------------------------- Summary ======= Processing a specially crafted IPv6 Type 0 Routing header can crash a device running Cisco IOS software. This vulnerability does not affect IPv6 Type 2 Routing header which is used in mobile IPv6. IPv6 is not enabled by default in Cisco IOS. Cisco has made free software available to address this vulnerability for affected customers. There are workarounds available to mitigate the effects of the vulnerability. The workaround depends on if Mobile IPv6 is used and what version on Cisco IOS is being currently used. This vulnerability was initially reported by a customer and further trigger vector was discovered during developing the fix for this vulnerability. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070124-IOS-IPv6.shtml. Affected Products ================= Devices running Cisco IOS and having IPv6 enabled on, at least, one of their interface may be affected by this vulnerability. Vulnerable Products +------------------ 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 IOS release 12.4(9.10): Cisco IOS Software, 7200 Software (C7200-JK9O3S-M), Version 12.4(9.10), INTERIM SOFTWARE Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2006 by Cisco Systems, Inc. Compiled Mon 29-May-06 04:42 by prod_rel_team Additional information about Cisco IOS release naming can be found at http://www.cisco.com/warp/public/620/1.html. Products Confirmed Not Vulnerable +-------------------------------- No other Cisco products are known to be vulnerable to the issue described in this Advisory. In particular Cisco IOS XR, Cisco PIX Appliance and Cisco MDS 9000 Series devices are not affected by this vulnerability. Details ======= This vulnerability can be triggered only when Cisco IOS processes specifically crafted IPv6 Type 0 Routing headers, which are used for source routing. Source routing is when an originator node explicitly specifies the exact path that a packet must take to reach the destination. Source routing is enabled by default on Cisco IOS if IPv6 is configured on the device. In order to trigger this vulnerability the packet must be destined to any of the IPv6 addresses defined on the device. The exact packet type is not relevant (e.g., TCP, ICMP, UDP) as the vulnerability is on the IP layer. For this reason care must be taken when implementing a workaround as this vulnerability can be triggered by a spoofed packet. IPv6 multicast packets can not be used to trigger this vulnerability. In addition to Type 0 Routing headers, IPv6 also supports Type 2 Routing that is used in Mobile IPv6 implementation. Type 2 Routing headers can not be used to trigger the vulnerability described in this Advisory. A router running vulnerable Cisco IOS software will process Type 0 Routing headers only if the destination address in the IPv6 packet is one of the IPv6 addresses defined on any of the interfaces. The address may be either a global (i.e., routable), loopback or link local address. Link local addresses are not supposed to be routable and they are valid only among directly connected devices. A device may also be susceptible in scenarios where IPv6 packets are tunneled over IPv4 networks provided that the IPv6 destination address (after de-encapsulation) is one of the IPv6 addresses defined on the device. This is independent of the exact encapsulation method used (e.g., MPLS, GRE or IPv6-in-IPv4). This vulnerability is documented in Cisco Bug IDs CSCsd40334 and CSCsd58381. Vulnerability Scoring Details +---------------------------- Cisco is providing scores for the vulnerabilities in this advisory based on the Common Vulnerability Scoring System (CVSS). Cisco will provide a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks. Cisco PSIRT will set the bias in all cases to normal. Customers are encouraged to apply the bias parameter when determining the environmental impact of a particular vulnerability. CVSS is a standards based scoring method that conveys vulnerability severity and helps determine urgency and priority of response. 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. Cisco Bug IDs: CSCsd40334 - IPv6 packet can cause crash CVSS Base Score: 10 Access Vector: Remote Access Complexity: Low Authentication: Not Required Confidentiality Impact: Complete Integrity Impact: Complete Availability Impact: Complete Impact Bias: Normal CVSS Temporal Score: 8.3 Exploitability: Functional Remediation Level: Official Fix Report Confidence: Confirmed CSCsd58381 - IPv6 routing header limitation CVSS Base Score: 10 Access Vector: Remote Access Complexity: Low Authentication: Not Required Confidentiality Impact: Complete Integrity Impact: Complete Availability Impact: Complete Impact Bias: Normal CVSS Temporal Score: 8.3 Exploitability: Functional Remediation Level: Official Fix Report Confidence: Confirmed Impact ====== Successful exploitation of the vulnerability listed in this Advisory can corrupt some memory structures. In most cases this will cause the affected device to crash and repeated exploitation could result in a sustained DoS attack. However, due to memory corruption, there is a potential to execute an arbitrary code. In the event of a successful remote code execution, device integrity will have been completely compromised. Software Version 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. Each row of the Cisco IOS software table (below) 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 (the "First Fixed Release") and the anticipated date of availability for each are listed in the "Rebuild" and "Maintenance" columns. 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. The release should be upgraded at least to the indicated release or a later version (greater than or equal to the First Fixed Release label). For more information on the terms "Rebuild" and "Maintenance," consult the following URL: http://www.cisco.com/warp/public/620/1.html. Please note: There are 3 IOS security advisories and one field notice being published on Jan 24th, 2007. Each advisory only lists the releases which fix the issue described in the advisory. A combined software table is available at http://www.cisco.com/warp/public/707/cisco-sa-20070124-bundle.shtml and can be used to choose a software release which fixes all security vulnerabilities published as of January 24th, 2007. The advisories and field notice published on January 24 are listed here. * http://www.cisco.com/warp/public/707/cisco-air-20070124-IOS-ipv6.shtml * http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-tcp.shtml * http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.sh… * http://www.cisco.com/warp/public/770/fn62613.shtml Requests for software rebuilds to include the change for Daylight Savings Time (DST) that will be implemented in March 2007 should be directed through the Technical Assistance Center (TAC) and this advisory should be used as reference. +-----------------------------------------------------------------------------+ | Major Release | Availability of Repaired Releases | |------------------------------+----------------------------------------------| | Affected 12.0-Based Release | Rebuild | Maintenance | |------------------------------+----------------------------------------------| | 12.0 | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0DA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0DB | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0DC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0S | 12.0(32)S3 | | |------------------------------+----------------------------------------------| | 12.0SC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0SL | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0SP | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0ST | Vulnerable; migrate to 12.0(32)S3 or later | |------------------------------+----------------------------------------------| | 12.0SX | Vulnerable for only 12.0(30)SX; contact TAC | |------------------------------+----------------------------------------------| | 12.0SY | | 12.0(32)SY | |------------------------------+----------------------------------------------| | 12.0SZ | Vulnerable; migrate to 12.0(32)S3 or later | |------------------------------+----------------------------------------------| | 12.0T | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0W | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0WC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0WT | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XB | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XD | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XE | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XF | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XG | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XH | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XI | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XJ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XK | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XL | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XM | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XN | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XQ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XR | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XS | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XV | Not vulnerable | |------------------------------+----------------------------------------------| | 12.0XW | Not vulnerable | |------------------------------+----------------------------------------------| | Affected 12.1-Based Release | Rebuild | Maintenance | |------------------------------+----------------------------------------------| | 12.1 | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1AA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1AX | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1AY | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1AZ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1CX | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1DA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1DB | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1DC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1E | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EB | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EO | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EU | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EV | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EW | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EX | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EY | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1EZ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1T | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XB | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XD | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XE | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XF | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XG | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XH | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XI | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XJ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XL | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XM | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XP | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XQ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XR | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XS | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XT | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XU | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.1XV | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.1XW | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XX | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XY | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1XZ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1YA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1YB | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.1YC | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.1YD | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.1YE | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1YF | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1YH | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1YI | Not vulnerable | |------------------------------+----------------------------------------------| | 12.1YJ | Not vulnerable | |------------------------------+----------------------------------------------| | Affected 12.2-Based Release | Rebuild | Maintenance | |------------------------------+----------------------------------------------| | 12.2 | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2B | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2BC | Vulnerable; migrate to 12.3(17b)BC3 or later | |------------------------------+----------------------------------------------| | 12.2BW | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2BY | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2BZ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2CX | Vulnerable; migrate to 12.3(17b)BC3 or later | |------------------------------+----------------------------------------------| | 12.2CY | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2CZ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2DA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2DD | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2DX | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2EU | Vulnerable; migrate to 12.2(25)EWA6 or later | |------------------------------+----------------------------------------------| | 12.2EW | Vulnerable; migrate to 12.2(25)EWA6 or later | |------------------------------+----------------------------------------------| | 12.2EWA | 12.2(25)EWA6 | | |------------------------------+----------------------------------------------| | 12.2EX | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2EY | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2EZ | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------------------------+----------------------------------------------| | 12.2FX | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2FY | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2FZ | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2IXA | Vulnerable; migrate to 12.2(18)IXB or later | |------------------------------+----------------------------------------------| | 12.2IXB | All 12.2IXB releases are fixed | |------------------------------+----------------------------------------------| | 12.2IXC | All 12.2IXC releases are fixed | |------------------------------+----------------------------------------------| | 12.2JA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2JK | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2MB | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2MC | 12.2(15)MC2h | | |------------------------------+---------------------+------------------------| | 12.2S | 12.2(25)S11 | 12.2(30)S | |------------------------------+---------------------+------------------------| | 12.2SB | 12.2(28)SB2 | 12.2(31)SB | |------------------------------+---------------------+------------------------| | 12.2SBC | 12.2(27)SBC4 | | |------------------------------+----------------------------------------------| | 12.2SEA | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------------------------+----------------------------------------------| | 12.2SEB | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------------------------+----------------------------------------------| | 12.2SEC | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------------------------+----------------------------------------------| | 12.2SED | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------------------------+----------------------------------------------| | 12.2SEE | 12.2(25)SEE1 | | |------------------------------+---------------------+------------------------| | 12.2SEF | 12.2(25)SEF1 | | |------------------------------+----------------------------------------------| | 12.2SEG | All 12.2SEG releases are fixed | |------------------------------+----------------------------------------------| | 12.2SG | 12.2(25)SG1 | 12.2(31)SG | |------------------------------+----------------------------------------------| | 12.2SGA | All 12.2SGA releases are fixed | |------------------------------+----------------------------------------------| | 12.2SO | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2SRA | All 12.2SRA releases are fixed | |------------------------------+----------------------------------------------| | 12.2SRB | All 12.2SRB releases are fixed | |------------------------------+----------------------------------------------| | 12.2SU | Vulnerable; migrate to 12.3(14)T7 or later | |------------------------------+----------------------------------------------| | 12.2SV | 12.2(25)SV3 | 12.2(26)SV | |------------------------------+---------------------+------------------------| | 12.2SW | 12.2(25)SW7 | | |------------------------------+----------------------------------------------| | 12.2SX | Vulnerable; migrate to 12.2(18)SXD7a or | | | later | |------------------------------+----------------------------------------------| | 12.2SXA | Vulnerable; migrate to 12.2(18)SXD7a or | | | later | |------------------------------+----------------------------------------------| | 12.2SXB | Vulnerable; migrate to 12.2(18)SXD7a or | | | later | |------------------------------+----------------------------------------------| | 12.2SXD | 12.2(18)SXD7a | | |------------------------------+---------------------+------------------------| | 12.2SXE | 12.2(18)SXE6 | | |------------------------------+---------------------+------------------------| | 12.2SXF | 12.2(18)SXF5 | | |------------------------------+----------------------------------------------| | 12.2SY | Vulnerable; migrate to 12.2(18)SXD7a or | | | later | |------------------------------+----------------------------------------------| | 12.2SZ | Vulnerable; migrate to 12.2(25)S11 or later | |------------------------------+----------------------------------------------| | 12.2T | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2TPC | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2XA | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XB | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XC | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2XD | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XE | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2XF | Vulnerable; migrate to 12.3(17b)BC3 or later | |------------------------------+----------------------------------------------| | 12.2XG | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XH | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XI | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XJ | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XK | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XL | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XM | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XN | | 12.2(31)XN | |------------------------------+----------------------------------------------| | 12.2XQ | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XR | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2XS | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XT | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XU | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XV | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2XW | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2YA | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2YB | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2YC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2YD | Vulnerable; migrate to 12.3(11)T10 or later | |------------------------------+----------------------------------------------| | 12.2YE | Vulnerable; migrate to 12.2(25)S11 or later | |------------------------------+----------------------------------------------| | 12.2YF | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2YG | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2YH | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2YJ | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2YK | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2YL | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YM | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YN | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YO | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2YP | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2YQ | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YR | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YT | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2YU | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YV | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YW | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YX | Vulnerable; migrate to 12.3(14)T7 or later | |------------------------------+----------------------------------------------| | 12.2YY | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2YZ | Vulnerable; migrate to 12.2(25)S11 or later | |------------------------------+----------------------------------------------| | 12.2ZA | Vulnerable; migrate to 12.2(18)SXD7a or | | | later | |------------------------------+----------------------------------------------| | 12.2ZB | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2ZC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2ZD | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2ZE | Vulnerable; migrate to 12.3(18) or later | |------------------------------+----------------------------------------------| | 12.2ZF | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2ZG | Not vulnerable | |------------------------------+----------------------------------------------| | 12.2ZH | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2ZJ | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2ZL | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2ZN | Vulnerable; migrate to 12.3(4)T13 or later | |------------------------------+----------------------------------------------| | 12.2ZP | Not vulnerable | |------------------------------+----------------------------------------------| | Affected 12.3-Based Release | Rebuild | Maintenance | |------------------------------+---------------------+------------------------| | 12.3 | 12.3(17b) | 12.3(18) | |------------------------------+----------------------------------------------| | 12.3B | Vulnerable; migrate to 12.3(11)T10 or later | |------------------------------+----------------------------------------------| | 12.3BC | 12.3(17b)BC3 | | |------------------------------+----------------------------------------------| | 12.3BW | Vulnerable; migrate to 12.3(11)T10 or later | |------------------------------+----------------------------------------------| | 12.3JA | Not vulnerable | |------------------------------+----------------------------------------------| | 12.3JEA | All 12.3JEA releases are fixed | |------------------------------+----------------------------------------------| | 12.3JEB | All 12.3JEA releases are fixed | |------------------------------+----------------------------------------------| | 12.3JK | Not vulnerable | |------------------------------+----------------------------------------------| | 12.3JX | Not vulnerable | |------------------------------+----------------------------------------------| | | 12.3(4)T13 | | | |---------------------+------------------------| | 12.3T | 12.3(11)T10 | | | |---------------------+------------------------| | | 12.3(14)T7 | | |------------------------------+----------------------------------------------| | 12.3TPC | Not vulnerable | |------------------------------+----------------------------------------------| | 12.3XA | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XB | Vulnerable; migrate to 12.3(11)T10 or later | |------------------------------+----------------------------------------------| | 12.3XC | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XD | Vulnerable; migrate to 12.3(11)T10 or later | |------------------------------+----------------------------------------------| | 12.3XE | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XF | Vulnerable; migrate to 12.3(11)T10 or later | |------------------------------+----------------------------------------------| | 12.3XG | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XH | Vulnerable; migrate to 12.3(11)T10 or later | |------------------------------+----------------------------------------------| | 12.3XI | 12.3(7)XI8a | 12.3(7)XI9 | |------------------------------+----------------------------------------------| | 12.3XJ | Vulnerable; migrate to 12.3(14)YX2 or later | |------------------------------+----------------------------------------------| | 12.3XK | Vulnerable; migrate to 12.3(14)T7 or later | |------------------------------+----------------------------------------------| | 12.3XQ | Vulnerable; migrate to 12.4(8) or later | |------------------------------+----------------------------------------------| | 12.3XR | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XS | Vulnerable; migrate to 12.4(8) or later | |------------------------------+----------------------------------------------| | 12.3XU | Vulnerable; migrate to 12.4(2)T4 or later | |------------------------------+----------------------------------------------| | 12.3XW | Vulnerable; migrate to 12.3(14)YX2 or later | |------------------------------+----------------------------------------------| | 12.3XX | Vulnerable; migrate to 12.4(8) or later | |------------------------------+----------------------------------------------| | 12.3XY | Not vulnerable | |------------------------------+----------------------------------------------| | 12.3YA | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3YD | Vulnerable; migrate to 12.4(2)T4 or later | |------------------------------+----------------------------------------------| | 12.3YF | Vulnerable; migrate to 12.3(14)YX2 or later | |------------------------------+----------------------------------------------| | 12.3YG | Vulnerable; migrate to 12.4(2)T4 or later | |------------------------------+----------------------------------------------| | 12.3YH | Vulnerable; migrate to 12.4(2)T4 or later | |------------------------------+----------------------------------------------| | 12.3YI | Vulnerable; migrate to 12.4(2)T4 or later | |------------------------------+----------------------------------------------| | 12.3YJ | Vulnerable; migrate to 12.4(6)T1 or later | |------------------------------+----------------------------------------------| | 12.3YK | Vulnerable; migrate to 12.4(4)T2 or later | |------------------------------+----------------------------------------------| | 12.3YM | 12.3(14)YM8 | | |------------------------------+----------------------------------------------| | 12.3YQ | Vulnerable; migrate to 12.4(6)T1 or later | |------------------------------+----------------------------------------------| | 12.3YS | Vulnerable; migrate to 12.4(4)T2 or later | |------------------------------+----------------------------------------------| | 12.3YT | Vulnerable; migrate to 12.4(4)T2 or later | |------------------------------+----------------------------------------------| | 12.3YU | Vulnerable; migrate to 12.4(2)XB2 or later | |------------------------------+----------------------------------------------| | 12.3YX | 12.3(14)YX2 | | |------------------------------+---------------------+------------------------| | 12.3YZ | 12.3(11)YZ1 | | |------------------------------+---------------------+------------------------| | Affected 12.4-Based Release | Rebuild | Maintenance | |------------------------------+---------------------+------------------------| | | 12.4(3d) | | | |---------------------+------------------------| | 12.4 | 12.4(5b) | | | |---------------------+------------------------| | | 12.4(7a) | 12.4(8) | |------------------------------+----------------------------------------------| | 12.4MR | Not vulnerable | |------------------------------+----------------------------------------------| | 12.4SW | All 12.4SW releases are fixed | |------------------------------+----------------------------------------------| | | 12.4(2)T4 | | | |---------------------+------------------------| | 12.4T | 12.4(4)T2 | | | |---------------------+------------------------| | | 12.4(6)T1 | 12.4(9)T | |------------------------------+----------------------------------------------| | 12.4XA | Vulnerable; migrate to 12.4(6)T1 or later | |------------------------------+----------------------------------------------| | 12.4XB | 12.4(2)XB2 | | |------------------------------+---------------------+------------------------| | 12.4XC | 12.4(4)XC5 | | |------------------------------+---------------------+------------------------| | 12.4XD | 12.4(4)XD2 | | |------------------------------+----------------------------------------------| | 12.4XE | All 12.4XE releases are fixed | |------------------------------+----------------------------------------------| | 12.4XG | All 12.4XG releases are fixed | |------------------------------+----------------------------------------------| | 12.4XJ | All 12.4XJ releases are fixed | |------------------------------+----------------------------------------------| | 12.4XP | All 12.4XP releases are fixed | |------------------------------+----------------------------------------------| | 12.4XT | All 12.4XT releases are fixed | +-----------------------------------------------------------------------------+ Workarounds =========== The workaround consists of filtering packets that contain Type 0 Routing header(s). Special attention must be paid not to filter packets with Type 2 Routing headers as that would break Mobile IPv6 deployment. Depending on what Cisco IOS software release is used and if Mobile IPv6 is deployed or not we have the following workarounds. As any packet type can be used to trigger this vulnerability the care must be taken when implementing a workaround to account for a spoofed packet. Additional mitigations that can be deployed on Cisco devices within the network are available in the Cisco Applied Intelligence companion document for this advisory: http://www.cisco.com/warp/public/707/cisco-air-20070124-IOS-IPv6.shtml Mobile IPv6 is not deployed +-------------------------- For IOS releases before 12.3(4)T the workaround is to use ACLs to filter all packets that contain Routing headers. This method can not distinguish between Type 0 and Type 2 Routing headers so it is not suitable if Mobile IPv6 is deployed. The following example shows how to configure such ACLs. Router(config)#ipv6 access-list deny-sourcerouted Router(config-ipv6-acl)#deny ipv6 any <myaddress1> routing Router(config-ipv6-acl)#deny ipv6 any <myaddress2> routing Router(config-ipv6-acl)#permit ipv6 any any Router(config-ipv6-acl)#exit Router(config)#interface Ethernet0 Router(config-if)#ipv6 traffic-filter deny-sourcerouted in In this example <myaddressX> is an IPv6 address. One example of such address is 2600:dead:beef:cafe:0:1:0:1111. The ACL must be applied to all interfaces and all IPv6 addresses that are configured. If an interface has more than one IPv6 address configured then all addresses must be covered by the ACLs. This also includes all loopback and "link local" addresses for each interface. The alternative of enumerating all IPv6 addresses is to use statement "deny ipv6 any any routing". While that simplifies the resulting ACL it will also filter all transit IPv6 traffic with Routing headers 0 and 2. The example where all configured IPv6 addresses are enumerated will not affect transit traffic. This comment is applicable to all other examples in this Advisory. Starting from the IOS release 12.2(15)T a new command "ipv6 source-route" was introduced. If applied, it will block any IPv6 packet with any IPv6 routing headers (both types 0 and 2). The configuration is given in the following example. Router(config)#no ipv6 source-route This is a global command and it applies to all interfaces. The command is applicable on all defined IPv6 addresses, including the link local and loopback address, and on all interfaces. Mobile IPv6 is deployed +---------------------- There is no workaround if you are running a Cisco IOS release prior to 12.4(2)T. In IOS 12.4(2)T a new keyword "routing-type" is added to IPv6 ACLs. It can be used to selectively permit or deny specific routing types. Router(config)#ipv6 access-list deny-sourcerouted Router(config-ipv6-acl)#deny ipv6 any <myaddress1> routing-type 0 Router(config-ipv6-acl)#permit ipv6 any any Router(config)#interface Ethernet0 Router(config-if)#ipv6 source-route Router(config-if)#ipv6 traffic-filter deny-sourcerouted in The filter must be applied to all interfaces that have IPv6 configured. Obtaining Fixed Software ======================== Cisco will make free software available to address this vulnerability for affected customers. This advisory will be updated as fixed software becomes available. 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/public/sw-license-agreement.html, or as otherwise set forth at Cisco.com Downloads at http://www.cisco.com/public/sw-center/sw-usingswc.shtml. Do not contact either "psirt(a)cisco.com" or "security-alert(a)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 agreement 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 who do not hold a Cisco service contract and customers who purchase through third-party vendors but are unsuccessful at obtaining fixed software through their point of sale should get their 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(a)cisco.com Have your product serial number available and give the URL of this notice as evidence of your entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC. Refer to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for additional TAC contact information, including special 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 initially reported to Cisco by Arnaud Ebalard from EADS Corporate Research Center. An additional vector to trigger it was discovered internally while fixing the vulnerability. 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-20070124-IOS-IPv6.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(a)cisco.com * first-teams(a)first.org * bugtraq(a)securityfocus.com * vulnwatch(a)vulnwatch.org * cisco(a)spot.colorado.edu * cisco(a)spot.colorado.edu * cisco-nsp(a)puck.nether.net * full-disclosure(a)lists.grok.org.uk * comp.dcom.sys.cisco(a)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 ================ +----------------------------------------+ | 1.0 | 2007-January-24 | Initial 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.…. This includes instructions for press inquiries regarding Cisco security notices. All Cisco security advisories are available at http://www.cisco.com/go/psirt. - ----------------------------------------------------------------------- All contents are Copyright 1992-2007 Cisco Systems, Inc. All rights reserved. - ----------------------------------------------------------------------- Updated: Jan 24, 2007 Document ID: 72372 - ----------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFt4q78NUAbBmDaxQRAnmUAKCddmt7R/tv6za5p5uaXzv3nJGAXQCeIh+Q VY3aC/IEoqWog0b4v3ji+is= =lzrx -----END PGP SIGNATURE-----

1 0

Cisco Security Advisory: Crafted TCP Packet Can Cause Denial of Service
by Cisco Systems Product Security Incident Response Team 24 Jan '07

24 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cisco Security Advisory: Crafted TCP Packet Can Cause Denial of Service Advisory ID: cisco-sa-20070124-crafted-tcp http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-tcp.shtml Revision 1.0 For Public Release 2007 January 24 1600 UTC (GMT) - --------------------------------------------------------------------- Summary ======= The Cisco IOS Transmission Control Protocol (TCP) listener in certain versions of Cisco IOS software is vulnerable to a remotely-exploitable memory leak that may lead to a denial of service condition. This vulnerability only applies to traffic destined to the Cisco IOS device. Traffic transiting the Cisco IOS device will not trigger this vulnerability. Cisco has made free software available to address this vulnerability for affected customers. This issue is documented as Cisco bug ID CSCek37177. There are workarounds available to mitigate the effects of the vulnerability. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-tcp.shtml Affected Products ================= Vulnerable Products +------------------ This issue affects all Cisco devices running Cisco IOS software. To be affected, devices must be configured to process Internet Protocol version 4 (IPv4) packets and receive TCP packets. Devices which run only Internet Protocol version 6 (IPv6) are not affected. This vulnerability is present in all unfixed versions of Cisco IOS software, including versions 9.x, 10.x, 11.x and 12.x. 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 release 12.2(14)S16 with an installed image name of C7200-IS-M: Cisco Internetwork Operating System Software IOS (tm) 7200 Software (C7200-IS-M), Version 12.2(14)S16, RELEASE SOFTWARE (fc1) The release train label is "12.2". The next example shows a product running IOS release 12.3(7)T12 with an image name of C7200-IK9S-M: Cisco IOS Software, 7200 Software (C7200-IK9S-M), Version 12.3(7)T12, RELEASE SOFTWARE (fc1) Additional information about Cisco IOS Banners is available at: http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_white_paper… Products Confirmed Not Vulnerable +-------------------------------- Cisco products that do not run IOS are unaffected by this vulnerability. Cisco IOS-XR is not affected. No other Cisco products are currently known to be affected by this vulnerability. Details ======= TCP is the transport layer protocol designed to provide connection-oriented, reliable delivery of a data stream. To accomplish this, TCP uses a mixture of flags to indicate state and sequence numbers to identify the order in which the packets are to be reassembled. TCP also provides a number, called an acknowledgement number, that is used to indicate the sequence number of the next packet expected. The full specification of the TCP protocol can be found at http://www.ietf.org/rfc/rfc0793.txt Cisco IOS devices that are configured to receive TCP packets are exposed to this issue. This Advisory does not apply to traffic that is transiting the device. Certain crafted packets destined to an IPv4 address assigned to a physical or virtual interface on a Cisco IOS device may cause the device to leak a small amount of memory. Over time, such a memory leak may lead to memory exhaustion and potentially degraded service. Although this is an issue with TCP, it is not required to complete the TCP 3-way handshake in order for the memory leak to be triggered. Therefore, TCP packets with a spoofed source address may trigger the leak. The following document contains additional information on how to identify if your router is suffering from a memory leak in Processor memory: http://www.cisco.com/warp/public/63/mallocfail.shtml#tshoot2 Vulnerability Scoring Details ============================= Cisco is providing scores for the vulnerabilities in this advisory based on the Common Vulnerability Scoring System (CVSS). Cisco will provide a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks. Cisco PSIRT will set the bias in all cases to normal. Customers are encouraged to apply the bias parameter when determining the environmental impact of a particular vulnerability. CVSS is a standards based scoring method that conveys vulnerability severity and helps determine urgency and priority of response. 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: http://intellishield.cisco.com/security/alertmanager/cvss Cisco Bug IDs: CSCek37177 CVSS Base Score: 3.3 Access Vector: Remote Access Complexity: Low Authentication: Not Required Confidentiality Impact: None Integrity Impact: None Availability Impact: Complete Impact Bias: Normal CVSS Temporal Score: 2.7 Exploitability: Functional Remediation Level: Official Fix Report Confidence: Confirmed Impact ====== Successful exploitation of the vulnerability may result in a small amount of processor memory to leak, which may lead to degraded service. This issue will not resolve over time, and will require a device reset to recover the leaked memory. This vulnerability only applies to traffic destined to the Cisco IOS device. Traffic transiting the device will not trigger this issue. Software Version 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. Each row of the Cisco IOS software table (below) 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 (the "First Fixed Release") and the anticipated date of availability for each are listed in the "Rebuild" and "Maintenance" columns. 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. The release should be upgraded at least to the indicated release or a later version (greater than or equal to the First Fixed Release label). For more information on the terms "Rebuild" and "Maintenance," consult the following URL: http://www.cisco.com/warp/public/620/1.html +------------------------------------------------------------------------+ | Major | Availability of Repaired Releases | | Release | | |------------+-----------------------------------------------------------| | Affected | | | | 12.0-Based | Rebuild | Maintenance | | Release | | | |------------+-----------------------------------------------------------| | 12.0 | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0DA | Vulnerable; migrate to 12.2(10)DA5 or later | |------------+-----------------------------------------------------------| | 12.0DB | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.0DC | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | | 12.0(31)S6 | | |12.0S |----------------------------+------------------------------| | | 12.0(32)S4 | | |------------+-----------------------------------------------------------| | 12.0SC | Vulnerable; migrate to 12.3(13a)BC6 or later | |------------+-----------------------------------------------------------| | 12.0SL | Vulnerable; migrate to 12.0(31)S6 or later | |------------+-----------------------------------------------------------| | 12.0SP | Vulnerable; migrate to 12.0(31)S6 or later | |------------+-----------------------------------------------------------| | 12.0ST | Vulnerable; migrate to 12.0(31)S6 or later | |------------+-----------------------------------------------------------| | 12.0SX | 12.0(25)SX11 | | |------------+----------------------------+------------------------------| | 12.0SY | | 12.0(32)SY | |------------+-----------------------------------------------------------| | 12.0SZ | Vulnerable; migrate to 12.0(31)S6 or later | |------------+-----------------------------------------------------------| | 12.0T | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0W | Not vulnerable | |------------+-----------------------------------------------------------| | 12.0WC | 12.0(5)WC15 | | |------------+-----------------------------------------------------------| | 12.0WT | Not vulnerable | |------------+-----------------------------------------------------------| | 12.0XA | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XB | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XC | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XD | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XE | Vulnerable; migrate to 12.1(26)E7 or later | |------------+-----------------------------------------------------------| | 12.0XF | Not vulnerable | |------------+-----------------------------------------------------------| | 12.0XG | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XH | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XI | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XJ | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XK | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XL | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XM | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XN | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XQ | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XR | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XS | Vulnerable; migrate to 12.1(26)E7 or later | |------------+-----------------------------------------------------------| | 12.0XV | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.0XW | Not vulnerable | |------------+-----------------------------------------------------------| | Affected | | | | 12.1-Based | Rebuild | Maintenance | | Release | | | |------------+-----------------------------------------------------------| | 12.1 | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1 AA | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1 AX | Vulnerable; migrate to 12.2(25)EY4 or later | |------------+-----------------------------------------------------------| | 12.1 AY | Vulnerable; migrate to 12.1(22)EA8 or later | |------------+-----------------------------------------------------------| | 12.1 AZ | Vulnerable; migrate to 12.1(22)EA8 or later | |------------+-----------------------------------------------------------| | 12.1 CX | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1 DA | Vulnerable; migrate to 12.2(10)DA5 or later | |------------+-----------------------------------------------------------| | 12.1 DB | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.1 DC | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | | 12.1(26)E7 | | |12.1E |----------------------------+------------------------------| | | 12.1(27b)E1 | | |------------+----------------------------+------------------------------| | 12.1EA | 12.1(22)EA8 | | |------------+-----------------------------------------------------------| | 12.1EB | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.1EC | Vulnerable; migrate to 12.3(13a)BC6 or later | |------------+-----------------------------------------------------------| | | 12.1(19)EO6; available on | | | 12.1EO | 31-Jan-07 | | | |----------------------------+------------------------------| | | 12.1(20)EO3 | | |------------+-----------------------------------------------------------| | 12.1EU | Vulnerable; migrate to 12.2(25)EWA6 or later | |------------+-----------------------------------------------------------| | 12.1EV | Vulnerable; migrate to 12.2(27)SV4 or later | |------------+-----------------------------------------------------------| | 12.1EW | Vulnerable; migrate to 12.2(25)EWA6 or later | |------------+-----------------------------------------------------------| | 12.1EX | Vulnerable; migrate to 12.1(26)E7 or later | |------------+-----------------------------------------------------------| | 12.1EY | Vulnerable; migrate to 12.1(26)E7 or later | |------------+-----------------------------------------------------------| | 12.1EZ | Vulnerable; migrate to 12.1(26)E7 or later | |------------+-----------------------------------------------------------| | 12.1T | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XA | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XB | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XC | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XD | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XE | Vulnerable; migrate to 12.1(26)E7 or later | |------------+-----------------------------------------------------------| | 12.1XF | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XG | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XH | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XI | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XJ | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XL | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XM | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XP | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XQ | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XR | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XS | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XT | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XU | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XV | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1XW | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XX | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XY | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1XZ | Vulnerable; migrate to 12.2(37) or later | |------------+-----------------------------------------------------------| | 12.1YA | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1YB | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1YC | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1YD | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1YE | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1YF | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1YH | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1YI | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.1YJ | Vulnerable; migrate to 12.1(22)EA8 or later | |------------+-----------------------------------------------------------| | Affected | | | | 12.2-Based | Rebuild | Maintenance | | Release | | | |------------+----------------------------+------------------------------| | 12.2 | | 12.2(37) | |------------+-----------------------------------------------------------| | 12.2B | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2BC | Vulnerable; migrate to 12.3(13a)BC6 or later | |------------+-----------------------------------------------------------| | 12.2BW | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2BY | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2BZ | Vulnerable; migrate to 12.3(7)XI8 or later | |------------+-----------------------------------------------------------| | 12.2CX | Vulnerable; migrate to 12.3(13a)BC6 or later | |------------+-----------------------------------------------------------| | 12.2CY | Vulnerable; migrate to 12.3(13a)BC6 or later | |------------+-----------------------------------------------------------| | 12.2CZ | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | | 12.2(10)DA5 | | |12.2DA |----------------------------+------------------------------| | | 12.2(12)DA10 | | |------------+-----------------------------------------------------------| | 12.2DD | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2DX | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2EU | Vulnerable; migrate to 12.2(25)EWA6 or later | |------------+-----------------------------------------------------------| | 12.2EW | Vulnerable; migrate to 12.2(25)EWA6 or later | |------------+-----------------------------------------------------------| | 12.2EWA | 12.2(25)EWA6 | | |------------+----------------------------+------------------------------| | 12.2EX | 12.2(25)EX1 | | |------------+----------------------------+------------------------------| | 12.2EY | 12.2(25)EY4 | | |------------+-----------------------------------------------------------| | 12.2EZ | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------+-----------------------------------------------------------| | 12.2FX | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------+-----------------------------------------------------------| | 12.2FY | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------+-----------------------------------------------------------| | 12.2FZ | All 12.2FZ releases are fixed | |------------+-----------------------------------------------------------| | 12.2IXA | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2IXB | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2IXC | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2JA | Vulnerable; migrate to 12.3(8)JA2 or later | |------------+-----------------------------------------------------------| | 12.2JK | Vulnerable; migrate to 12.4(4)T4 or later | |------------+-----------------------------------------------------------| | 12.2MB | Vulnerable; migrate to 12.2(25)SW8 or later | |------------+-----------------------------------------------------------| | 12.2MC | Vulnerable; migrate to 12.3(11)T11 or later | |------------+-----------------------------------------------------------| | 12.2S | 12.2(25)S12; Available | | | | 12-Feb-07 | | |------------+----------------------------+------------------------------| | 12.2SB | 12.2(28)SB2 | 12.2(31)SB | |------------+----------------------------+------------------------------| | 12.2SBC | 12.2(27)SBC5 | | |------------+----------------------------+------------------------------| | 12.2SE | | 12.2(35)SE | |------------+-----------------------------------------------------------| | 12.2SEA | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------+-----------------------------------------------------------| | 12.2SEB | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------+-----------------------------------------------------------| | 12.2SEC | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------+-----------------------------------------------------------| | 12.2SED | Vulnerable; migrate to 12.2(25)SEE1 or later | |------------+-----------------------------------------------------------| | 12.2SEE | 12.2(25)SEE1 | | |------------+----------------------------+------------------------------| | 12.2SEF | 12.2(25)SEF1 | | |------------+-----------------------------------------------------------| | 12.2SEG | All 12.2SEG releases are fixed | |------------+-----------------------------------------------------------| | 12.2SG | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2SGA | All 12.2SGA releases are fixed | |------------+-----------------------------------------------------------| | 12.2SO | 12.2(18)SO7 | | |------------+-----------------------------------------------------------| | 12.2SRA | All 12.2SRA releases are fixed | |------------+-----------------------------------------------------------| | 12.2SRB | All 12.2SRB releases are fixed | |------------+-----------------------------------------------------------| | 12.2SU | Vulnerable; migrate to 12.4(8) or later | |------------+-----------------------------------------------------------| | | 12.2(27)SV4 | | | |----------------------------+------------------------------| | 12.2SV | 12.2(28)SV1 | | | |----------------------------+------------------------------| | | 12.2(29)SV1 | | |------------+----------------------------+------------------------------| | 12.2SW | 12.2(25)SW8 | | |------------+-----------------------------------------------------------| | 12.2SX | Vulnerable; migrate to 12.2(18)SXD7a or later | |------------+-----------------------------------------------------------| | 12.2SXA | Vulnerable; migrate to 12.2(18)SXD7a or later | |------------+-----------------------------------------------------------| | 12.2SXB | Vulnerable; migrate to 12.2(18)SXD7a or later | |------------+-----------------------------------------------------------| | 12.2SXD | 12.2(18)SXD7a | | |------------+----------------------------+------------------------------| | 12.2SXE | 12.2(18)SXE6 | | |------------+----------------------------+------------------------------| | 12.2SXF | 12.2(18)SXF5 | | |------------+-----------------------------------------------------------| | 12.2SY | Vulnerable; migrate to 12.2(18)SXD7a or later | |------------+-----------------------------------------------------------| | 12.2SZ | Vulnerable; migrate to 12.2(25)S12 or later; Available | | | 12-Feb-07 | |------------+-----------------------------------------------------------| | 12.2T | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2TPC | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2XA | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XB | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XC | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2XD | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XE | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XF | Vulnerable; migrate to 12.3(13a)BC6 or later | |------------+-----------------------------------------------------------| | 12.2XG | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XH | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XI | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XJ | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XK | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XL | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XM | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XN | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XQ | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XR | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XS | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XT | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XU | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XV | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2XW | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YA | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YB | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YC | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YD | Vulnerable; migrate to 12.3(11)T11 or later | |------------+-----------------------------------------------------------| | 12.2YE | Vulnerable; migrate to 12.2(25)S12 or later; Available | | | 12-Feb-07 | |------------+-----------------------------------------------------------| | 12.2YF | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YG | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YH | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YJ | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YK | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YL | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YM | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YN | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YO | Not vulnerable | |------------+-----------------------------------------------------------| | 12.2YP | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YQ | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YR | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YS | Not vulnerable | |------------+-----------------------------------------------------------| | 12.2YT | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2YU | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YV | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YW | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YX | Vulnerable; migrate to 12.4(8) or later | |------------+-----------------------------------------------------------| | 12.2YY | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2YZ | Vulnerable; migrate to 12.2(25)S12 or later; Available | | | 12-Feb-07 | |------------+-----------------------------------------------------------| | 12.2ZA | Vulnerable; migrate to 12.2(18)SXD7a or later | |------------+-----------------------------------------------------------| | 12.2ZB | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2ZC | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2ZD | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2ZE | Vulnerable; migrate to 12.3(19) or later | |------------+-----------------------------------------------------------| | 12.2ZF | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2ZG | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2ZH | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2ZJ | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2ZL | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.2ZN | Vulnerable; migrate to 12.3(4)T13 or later | |------------+-----------------------------------------------------------| | 12.2ZP | Vulnerable; migrate to 12.4(8) or later | |------------+-----------------------------------------------------------| | Affected | | | | 12.3-Based | Rebuild | Maintenance | | Release | | | |------------+----------------------------+------------------------------| | 12.3 | 12.3(10f) | 12.3(19) | |------------+-----------------------------------------------------------| | 12.3B | Vulnerable; migrate to 12.3(11)T11 or later | |------------+-----------------------------------------------------------| | | 12.3(13a)BC6 | | |12.3BC |----------------------------+------------------------------| | | 12.3(17a)BC2 | | |------------+-----------------------------------------------------------| | 12.3BW | Vulnerable; migrate to 13.3(11)T11 or later | |------------+-----------------------------------------------------------| | 12.3JA | 12.3(8)JA2 | | |------------+-----------------------------------------------------------| | 12.3JEA | All 12.3JEA releases are fixed | |------------+-----------------------------------------------------------| | 12.3JEB | All 12.3JEB releases are fixed | |------------+-----------------------------------------------------------| | 12.3JK | 12.3(2)JK2 | | |------------+----------------------------+------------------------------| | 12.3JX | 12.3(7)JX4 | 12.3(11)JX | |------------+----------------------------+------------------------------| | | 12.3(4)T13 | | |12.3T |----------------------------+------------------------------| | | 12.3(11)T11 | | |------------+-----------------------------------------------------------| | 12.3TPC | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.3XA | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.3XB | Vulnerable; migrate to 12.3(11)T11 or later | |------------+-----------------------------------------------------------| | 12.3XC | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.3XD | Vulnerable; migrate to 12.3(11)T11 or later | |------------+-----------------------------------------------------------| | 12.3XE | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.3XF | Vulnerable; migrate to 12.3(11)T11 or later | |------------+-----------------------------------------------------------| | 12.3XG | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.3XH | Vulnerable; migrate to 12.3(11)T11 or later | |------------+-----------------------------------------------------------| | 12.3XI | 12.3(7)XI8 | | |------------+-----------------------------------------------------------| | 12.3XJ | Vulnerable; migrate to 12.3(14)YX2 or later | |------------+-----------------------------------------------------------| | 12.3XK | Vulnerable; migrate to 12.4(8) or later | |------------+-----------------------------------------------------------| | 12.3XQ | Vulnerable; migrate to 12.4(8) or later | |------------+-----------------------------------------------------------| | 12.3XR | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.3XS | Vulnerable; migrate to 12.4(8) or later | |------------+-----------------------------------------------------------| | 12.3XU | Vulnerable; migrate to 12.4(2)T5 or later | |------------+-----------------------------------------------------------| | 12.3XW | Vulnerable; migrate to 12.3(14)YX2 or later | |------------+-----------------------------------------------------------| | 12.3XX | Vulnerable; migrate to 12.4(8) or later | |------------+-----------------------------------------------------------| | 12.3XY | Vulnerable; migrate to 12.4(8) or later | |------------+-----------------------------------------------------------| | 12.3YA | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.3YD | Vulnerable; migrate to 12.4(2)T5 or later | |------------+-----------------------------------------------------------| | 12.3YF | Vulnerable; migrate to 12.3(14)YX2 or later | |------------+-----------------------------------------------------------| | 12.3YG | Vulnerable; migrate to 12.4(2)T5 or later | |------------+-----------------------------------------------------------| | 12.3YH | Vulnerable; migrate to 12.4(2)T5 or later | |------------+-----------------------------------------------------------| | 12.3YI | Vulnerable; migrate to 12.4(2)T5 or later | |------------+-----------------------------------------------------------| | 12.3YJ | Vulnerable; migrate to 12.3(14)YQ8 or later | |------------+-----------------------------------------------------------| | 12.3YK | Vulnerable; migrate to 12.4(4)T4 or later | |------------+-----------------------------------------------------------| | 12.3YM | 12.3(14)YM8 | | |------------+----------------------------+------------------------------| | 12.3YQ | 12.3(14)YQ8 | | |------------+-----------------------------------------------------------| | 12.3YS | Vulnerable; migrate to 12.4(4)T4 or later | |------------+-----------------------------------------------------------| | 12.3YT | Vulnerable; migrate to 12.4(4)T4 or later | |------------+-----------------------------------------------------------| | 12.3YU | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.3YX | 12.3(14)YX2 | | |------------+----------------------------+------------------------------| | 12.3YZ | 12.3(11)YZ1 | | |------------+----------------------------+------------------------------| | Affected | | | | 12.4-Based | Rebuild | Maintenance | | Release | | | |------------+----------------------------+------------------------------| | | 12.4(3e) | | |12.4 |----------------------------+------------------------------| | | 12.4(7b) | 12.4(8) | |------------+----------------------------+------------------------------| | 12.4MR | 12.4(6)MR1 | | |------------+-----------------------------------------------------------| | 12.4SW | All 12.4SW releases are fixed | |------------+-----------------------------------------------------------| | | 12.4(2)T5 | | | |----------------------------+------------------------------| | 12.4T | 12.4(4)T4 | | | |----------------------------+------------------------------| | | 12.4(6)T3 | 12.4(9)T | |------------+-----------------------------------------------------------| | 12.4XA | Vulnerable; migrate to 12.4(6)T3 | |------------+-----------------------------------------------------------| | 12.4XB | Vulnerable; contact TAC | |------------+-----------------------------------------------------------| | 12.4XC | 12.4(4)XC3 | | |------------+----------------------------+------------------------------| | 12.4XD | 12.4(4)XD4 | | |------------+-----------------------------------------------------------| | 12.4XE | All 12.4XE releases are fixed | |------------+-----------------------------------------------------------| | 12.4XG | All 12.4XG releases are fixed | |------------+-----------------------------------------------------------| | 12.4XJ | All 12.4XJ releases are fixed | |------------+-----------------------------------------------------------| | 12.4XP | All 12.4XP releases are fixed | |------------+-----------------------------------------------------------| | 12.4XT | All 12.4XT releases are fixed | +------------------------------------------------------------------------+ Workarounds =========== Additional mitigations that can be deployed on Cisco devices within the network are available in the Cisco Applied Intelligence companion document for this advisory: http://www.cisco.com/warp/public/707/cisco-air-20070124-crafted-tcp.shtml Note: Configuring VTY access-class filters is not an effective mitigation strategy for this vulnerability. Infrastructure ACLs (iACL) +------------------------- Although it is often difficult to block traffic transiting your network, it is possible to identify traffic which should never be allowed to target your infrastructure devices and block that traffic at the border of your network. Infrastructure ACLs are considered 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 ACL example shown below should be included as part of the deployed infrastructure access-list which will protect all devices with IP addresses in the infrastructure IP address range. A sample access list for devices running Cisco IOS is below: !--- Permit TCP services from trust hosts destined !--- to infrastructure addresses. access-list 150 permit tcp TRUSTED_HOSTS MASK INFRASTRUCTURE_ADDRESSES MASK !--- Deny TCP packets from all other sources destined to infrastructure addresses. access-list 150 deny tcp any INFRASTRUCTURE_ADDRESSES MASK !--- 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 here: http://www.cisco.com/warp/public/707/iacl.html Receive ACLs (rACL) +------------------ For distributed platforms, Receive ACLs may be an option starting in Cisco IOS Software Versions 12.0(21)S2 for the 12000 (GSR), 12.0(24)S for the 7500, and 12.0(31)S for the 10720. The Receive ACL protects the device from harmful traffic before the traffic can impact the route processor. Receive ACLs are designed to only protect the device on which it is configured. On the 12000, transit traffic is never affected by a receive ACL. Because of this, the destination IP address "any" used in the example ACL entries below only refer to the router's own physical or virtual IP addresses. On the 7500 and 10720, transit traffic with IP options set will be subject to the Receive ACL and permitted or denied accordingly. Receive ACLs are considered 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 white paper entitled "GSR: Receive Access Control Lists" will help you identify and allow legitimate traffic to your device and deny all unwanted packets: http://www.cisco.com/warp/public/707/racl.html The following is the receive path ACL written to permit this type of traffic from trusted hosts: !--- Permit tcp services from trusted hosts allowed to the RP. access-list 151 permit tcp TRUSTED_ADDRESSES MASK any !--- Deny tcp services from all other sources to the RP. access-list 151 deny tcp any any !--- Permit all other traffic to the RP. access-list 151 permit ip any any !--- Apply this access list to the 'receive' path. ip receive access-list 151 Control Plane Policing (CoPP) +---------------------------- The Control Plane Policing (CoPP) feature may be used to mitigate this vulnerability. In the following example, only TCP traffic from trusted hosts and with 'receive' destination IP addresses is permitted to reach the route processor (RP). All other 'transit' IP traffic is unaffected. It should be noted that dropping traffic from unknown or untrusted IP addresses may affect hosts with dynamically assigned IP addresses from connecting to the Cisco IOS device. access-list 152 deny tcp TRUSTED_ADDRESSES MASK any access-list 152 permit tcp any any access-list 152 deny ip any any ! class-map match-all permit-tcp-class match access-group 152 ! ! policy-map permit-tcp-policy class permit-tcp-class drop ! control-plane service-policy input permit-tcp-policy In the above CoPP example, the ACL entries that match the 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 are not affected by the policy-map drop function. Please note that in the 12.2S and 12.0S Cisco IOS trains the policy-map syntax is different: policy-map permit-tcp-policy class class permit-tcp-class police 32000 1500 1500 conform-action drop exceed-action drop CoPP is available in Cisco IOS release trains 12.0S, 12.2SX, 12.2S, 12.3T, 12.4, and 12.4T. Additional information on the configuration and use of the CoPP feature can be found at the following URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1838/products_white_paper… Anti-spoofing +------------ The Unicast Reverse Path Forwarding (Unicast RPF or uRPF) feature helps to mitigate problems that are caused by spoofed IP source addresses. It is available on Cisco routers and firewalls. For further details, please refer to: http://www.cisco.com/en/US/partner/products/ps6441/products_command_referen… By enabling Unicast Reverse Path Forwarding (uRPF), all spoofed packets will be dropped at the first device. To enable uRPF, use the following commands. router(config)# ip cef router(config)# interface interface # router(config-if)# ip verify unicast source reachable-via rx BGP and BTSH/GTSM +---------------- Depending on your release of software, it may be possible to protect your BGP sessions from this memory leak. With the introduction of CSCee73956, Cisco IOS has improved support for BTSH (BGP TTL Security Hack) to reduce, if not eliminate a risk of a memory leak due to this vulnerability. This functionality is also known as GTSM (Generalized TTL Security Mechanism) and documented in RFC 3682. This section refers to GTSM as applied to eBGP sessions only. Releases of Cisco IOS that contain CSCee73956 are protected from this attack against the BGP port (TCP port 179) only. Other ports should be protected accordingly. BTSH is not supported for iBGP sessions. BTSH was first introduced in Cisco IOS in 12.0(27)S, 12.3(7)T and 12.2(25)S. Note that the BTSH feature prior to CSCee73956 will not protect against this vulnerability. For more information on BTSH, please see: http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/12… Obtaining Fixed Software ======================== Cisco will make free software available to address this vulnerability for affected customers. This advisory will be updated as fixed software becomes available. 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/public/sw-license-agreement.html, or as otherwise set forth at Cisco.com Downloads at http://www.cisco.com/public/sw-center/sw-usingswc.shtml. Do not contact either "psirt(a)cisco.com" or "security-alert(a)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 agreement 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 who do not hold a Cisco service contract and customers who purchase through third-party vendors but are unsuccessful at obtaining fixed software through their point of sale should get their 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(a)cisco.com Have your product serial number available and give the URL of this notice as evidence of your entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC. Refer to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for additional TAC contact information, including special 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 by Cisco during our internal testing process. 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-20070124-crafted-tcp.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(a)cisco.com * first-teams(a)first.org * bugtraq(a)securityfocus.com * vulnwatch(a)vulnwatch.org * cisco(a)spot.colorado.edu * cisco-nsp(a)puck.nether.net * full-disclosure(a)lists.grok.org.uk * comp.dcom.sys.cisco(a)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 ================ +---------------------------------------+ | | | Initial | | 1.0 | 2007-January-24 | 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.… 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----- Version: GnuPG v1.4.5 (SunOS) iD8DBQFFt3qK8NUAbBmDaxQRAlmUAJ4orT3YO8RntAsyzsx8C/JL/q7QoQCfRcaq 83G2Nzt3qRHKu3ZD/6I6gck= =OTe7 -----END PGP SIGNATURE-----

1 0

DNS Query Question
by Dennis Dayman 24 Jan '07

24 Jan '07

I have a customer having some DNS issues. They have done some research regarding some DNS timeout errors they saw with Verizon's sender verify looking up their MX records. What they have discovered is their current DNS service has a 1% failure/timeout rate. They are exploring other vendors (UltraDNS for one), but need an estimate of the number of DNS queries for accurate pricing to put together a ROI argument for the switch. I have no IDEA if this can be determined, but what is a good estimate of the number of DNS queries generated from sending an email? I know that it may differ from ISP to ISP, but they just need a rough number for pricing purposes. If you also happen to know how many DNS requests make it to the root server (rather than a cached proxy out on the net), that would be great. -Dennis

4 7

Undersea fiber cut after Taiwan earthquake - PCCW / Singtel / KT e tc connectivity disrupted
by Rod Beck 23 Jan '07

23 Jan '07

What's really interesing is the fragility of the existing telecom infrastructure. These six cables were apparently very close to each other in the water. In other words, despite all the preaching about physical diversity, it was ignored in practice. Indeed, undersea cables very often use the same conduits for terrestrial backhaul since it is the most cost effective solution. However, that means that diversifying across undersea cables does not buy the sort of physical diversity that is anticipated. Roderick S. Beck EMEA and North American Sales Hibernia Atlantic rod.beck(a)hiberniaatlantic.com http://www.hiberniaatlantic.com This e-mail and any attachments thereto is intended only for use by the addressee(s) named herein and may be proprietary and/or legally privileged. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this email, and any attachments thereto, without the prior written permission of the sender is strictly prohibited. If you receive this e-mail in error, please immediately telephone or e-mail the sender and permanently delete the original copy and any copy of this e-mail, and any printout thereof. All documents, contracts or agreements referred or attached to this e-mail are SUBJECT TO CONTRACT. The contents of an attachment to this e-mail may contain software viruses that could damage your own computer system. While Hibernia Atlantic has taken every reasonable precaution to minimize this risk, we cannot accept liability for any damage that you sustain as a result of software viruses. You should carry out your own virus checks before opening any attachment

11 17