- NANOG - lists.nanog.org

Re: Akamai an Inside Job?
by Brian Mulvaney 16 Jun '04

16 Jun '04

At 08:23 AM 6/16/2004, David Kennedy CISSP wrote: >http://www.overclockersclub.com/?read=8733819 > >The Akamai attacks started in the morning and it was detected by >Keynote Systems, a web tracking company that is able to track the load >and bandwidth on the Internet. According to Keynote they saw >an "Internet performance issue" this morning Keynote's primary business model is measuring the performance and availability of public web sites as seen from a distributed network of synthetic probes. They don't offer any services that "track the load and bandwidth on the Internet". Here's what their public/PR type email alert said on the matter yesterday: Keynote Internet Performance Alert Starting at approximately 5:30am PDT today, a major Internet performance issue was detected by Keynote systems. By 6:00am, the availability of the Keynote Business 40 Internet Performance Index had dropped from its usual near-100% availability to 81% availability: <http://keynote.lyris.net/t/4086/732513/23/0/>http://web507.keynote.com/mykeynote/Post/KB40data_061504_085844.asp Further analysis by Keynote indicated that the availability issues were limited to several large sites, all of whom outsource their DNS services to Akamai. These sites dropped to near-zero availability: <http://keynote.lyris.net/t/4086/732513/24/0/>http://web507.keynote.com/mykeynote/Post/KB40data_061504_090509.asp Availability was largely restored by approximately 7:45am PDT. >... >They have tracked the attacker back to person that is at the Akamai >Technologies ISP. No other information has been given to us at this >time. We do not know if the FBI is working on this issue right now, but >we expect them to do so. > >[DMK: Source, beyond overclockers, unknown, reliability and accuracy unknown.] That's nonsense David. Keynote measurements can distinguish between availability problems caused by DNS outages versus those caused by connectivity or site outages. They manifestly don't track attackers. Brian Mulvaney

2 1

Asia Pacific Peering Guidebook Reviewer Request
by William B. Norton 16 Jun '04

16 Jun '04

Hi all - If you have no interest in Internet Peering in Asia, read no further. Otherwise,... Over the last year I have been working with the Peering Coordinator Community, particularly those that have built into and throughout Asia, to document what is *different* about peering in Asia as compared to say the U.S. and Europe. In February of this year I pulled together a group of Peering Coordinators for the APRICOT Peering Track. I asked them to share Peering processes that they found different, interesting, counter intuitive, or unexpected. This white paper documents the lessons learned and insights gained from Peering Coordinators experienced with peering in Asia. The Asia Pacific Peering Guidebook follows the path set by "The Evolution of the US Peering Ecosystem" white paper that I presented at the last NANOG, but focuses on the common dynamics and experiences that folks shared with me over the last year and at the APRICOT Peering Track. First, the paper documents what I call the "Foreign Tier 1 Peering Dynamic" that casts a Tier 1 ISP in one Peering Ecosystem as a Tier 2 ISP in another. We focus on the motivations, the reasons why this occurs as ISPs expand globally. Next, Peering Coordinators shared five reasons that they expanded into/within Asia: 1) Incumbent Tier 1 ISPs to peer their routes outside their home market 2) Meet US Tier 1 ISP Peering Prerequisites 3) Customers want them in Asia 4) Global Marketing Benefits 5) Sell transit in a more attractive transit market using four methods of interconnection: 1) Extend into foreign country 2) reciprically peer in each others coountry 3) Half-Circuit peering 4) Buy an ISP with Tier 1 peering in the foreign ecosystem The Peering Coordinators shared nine lessons, things they wish they had known before expanding into Asia: 1) Tier 1 ISPs will not want to peer in their home market 2) There are several challenges peering in Asia 2a) Peering Process is different - peering@ does not uniformly work 2b) Many language zones 2c) Many time zones - logisitics issues here 2d) Oceans add cost, latency - transpacific transport prices estimated in the paper 2e) local loops still a major expense 2f) transit prices highly variable across countries in Asia - transit street prices quoted 3) Creative peering deals 4) Watch for Inadvertent Tromboning 5) Local Presence is required 6) Separation of Int'l Transit from Domestic Transit in some markets 7) Content that transcends the language barrier is not allowed to be hosted in country 8) No true regional content in Asia 9) Content Peering works in Asia 10) Understand the Internet Peering Ecosystem prior to building in On this last point, the paper enumerates several data points including naming the Tier 1's, the emerging broadband players, the peering inclinations, etc. for Hong Kong, Tokyo, Sydney and Singapore. Some of the Yahoo!Broadband activities for example in Japan show that some places in Asia are leap-frogging the US in terms of next-gen access bandwidth. How would you like 40Mbps DSL access for $50/mo or FTTH for $100/mo? I'm at the point where I'd like to do a dozen or so final paper walk-throughs, where I email the white paper and walk interested folks through the paper to solicit comments and suggestions. I've found that talking people through the paper is this is the most effective way for me to make sure the paper (and subsequent presentation) flow well, and also increases the likelihood of me getting some feedback. If you have any interest in the topic and can spare about 30 minutes for a walkthrough over the next few weeks, send me a note and let's schedule a time I can talk you through the paper. I'm also planning a group walk through (a concall basically) towards the end of the month. As with all the Peering White Papers, this one will be made freely available to the community when it is finished. Bill Here are the other Peering White Papers that are available (google for "William B. Norton" to find them on the web, or email wbn(a)equinix.com with the white paper title in the subject line and I'll send you the latest version of the white paper.) 1. Interconnection Strategies for ISPs documents two dominant methods ISPs use to interconnect their networks. Over 200 ISPs helped create this white paper to identify when Internet Exchange Points make sense and the Direct Circuit interconnect method makes sense. Financial Models included in the paper quantify the tradeoffs between these two methods. All relevant data points are footnoted as to source. 2. Internet Service Providers and Peering answers the questions: "What is Peering and Transit? What are the motivations for Peering? What is the ISP Peering Coordinators Process for obtaining peering? What are criteria for IX selection?" 3. A Business Case for Peering builds upon the previous white papers but focuses on the questions important to the Chief Financial Officer: "When does Peering make sense from a financial standpoint? When do all the costs of Peering get completely offset by the cost savings?" 4. The Art of Peering: The Peering Playbook builds on the previous white papers by asking the Peering Coordinators to share the "Tricks of the Trade", methods of getting peering where otherwise they might not be able to get peering. These 20 tactics range from the straight forward to the obscure, from the clever to the borderline unethical. Nonetheless, Peering Coordinators might be interested in field-proven effective ways of obtaining peering in this highly controversial white paper. 5. The Peering Simulation Game finishes up my half day Peering Tutorial by engaging the audience in the role of the Peering Coordinator. Each ISP in turn rolls the dice, expands their network, collects revenue for each square of customer traffic, and pays transit fees to their upstream ISP. They quickly learn that if they peer with each other, the costs of traffic exchange are much less, but they need to negotiate how to cover the costs of the interconnect. ISP Peering coordinators have commented on how close the peering simulation game is to reality in terms of the dialog that takes place. 6. Do ATM-based Internet Exchange Points Make Sense Anymore? Applies the "Business Case for Peering" financial models to ATM and Ethernet-based IXes using current market prices for transit, transport, and IX Peering Costs. 7. The Evolution of the U.S. Peering Ecosystem, introduces and focuses on several fundamental changes in the Peering Ecosystem spurred by several events following the telecom collapse of 1999/2000. 8. The Art of Peering: The IX Playbook follows the same tact as The Peering Playbook; we first introduce the framework theory of how and why IXes are valuable from an economic perspective. We then enumerate about a dozen tactics IXes use to get over the "Start Up Hump", to build a strong critical mass of participants, and finally, defense tactics to maintain that population. (To be released at a future date.)

1 0

RE: Akamai an Inside Job?
by dunger-nanog1087＠mailblocks.com 16 Jun '04

16 Jun '04

David Kennedy CISSP wrote: > The Akamai attacks started in the morning and it was detected by > Keynote Systems, a web tracking company that is able to track the load > and bandwidth on the Internet. According to Keynote they saw > an "Internet performance issue" this morning > ... Here's a link to a Reuter's article with official quotes from Keynote Systems: http://biz.yahoo.com/rc/040615/tech_internet_1.html Keynote saw availability of Yahoo, Microsoft and Google drop to near-zero. I have no clue where David got the information that: > They have tracked the attacker back to person that is at the Akamai > Technologies ISP. No other information has been given to us at this > time. That tidbit didn't come from Keynote. Can you provide a link, David? -DaveU

2 1

Re: Akamai DNS Issue?
by Stewart, William C (Bill), RTSLS 16 Jun '04

16 Jun '04

Daniel Golding suggested that the problem was that many folks are sharing Akamai's magic DNS algorithms. This doesn't appear to be a problem with magic algorithms - it appears that they're sharing the _servers_, and that the reported attack on the servers means that it doesn't matter how magic the algorithms are. Good luck to them on developing a longer-term workaround for the next attack. Bill Stewart, bill.stewart(a)pobox.com Disclaimer: This note is, as usual, my personal opinion, not my employer's.

5 5

Cisco Security Advisory: Cisco IOS Malformed BGP packet causes reload
by Cisco Systems Product Security Incident Response Team 16 Jun '04

16 Jun '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cisco Security Advisory: Cisco IOS Malformed BGP Packet Causes Reload Revision 1.0 ============ Last Updated June 16 15:00 UTC (GMT) For Public Release 2004 June 16 15:00 UTC (GMT) - ------------------------------------------------------------------------------- Please provide your feedback on this document. - ------------------------------------------------------------------------------- Contents Summary Affected Products Details Impact Software Versions and Fixes Obtaining Fixed Software Workarounds Exploitation and Public Announcements Status of This Notice: FINAL Distribution Revision History Cisco Security Procedures - ------------------------------------------------------------------------------- Summary ======= A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. Cisco has made free software available to address this problem. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml. Affected Products ================= Vulnerable Products This issue affects all Cisco devices running any unfixed version of Cisco IOS code and configured for BGP routing. A router which is running the BGP process will have a line in the config defining the AS number, which can be seen by issuing the command show running-config: router bgp <AS number> This vulnerability is present in any unfixed version of IOS, from the beginning of support for the BGP protocol, 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 IOS release 12.0(3) with an installed image name of C2500-IS-L: Cisco Internetwork Operating System Software IOS (TM) 2500 Software (C2500-IS-L), Version 12.0(3), RELEASE SOFTWARE The release train label is "12.0." The next example shows a product running IOS release 12.0(2a)T1 with an image name of C2600-JS-MZ: Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-JS-MZ), Version 12.0(2a)T1, RELEASE SOFTWARE (fc1) Additional information about Cisco IOS release naming can be found at http://www.cisco.com/warp/public/620/1.html. Products Confirmed Not Vulnerable Products confirmed not to be vulnerable include devices which cannot participate in BGP or cannot be configured for BGP. Details ======= The Border Gateway Protocol (BGP) is a routing protocol defined by RFC 1771, and designed to manage IP routing in large networks. An affected Cisco device running a vulnerable version of Cisco IOS software and enabling the BGP protocol will reload when a malformed BGP packet is received. BGP runs over TCP, a reliable transport protocol which requires a valid three way handshake before any further messages will be accepted. The Cisco IOS implementation of BGP requires the explicit definition of a neighbor before a connection can be established, and traffic must appear to come from that neighbor. These implementation details make it very difficult to send a BGP packet to a Cisco IOS device from an unauthorized source. A Cisco device receiving an invalid BGP packet will reset and may take several minutes to become fully functional. This vulnerability may be exploited repeatedly resulting in an extended DOS attack. This issue is documented in bug IDs CSCdu53656 and CSCea28131. Impact ====== Successful exploitation of this vulnerability results in a reload of the device. Repeated exploitation could result in a sustained DoS attack. Software Versions and Fixes =========================== Note: Many of the releases in this table were fixed prior to the release of other IOS advisories. Read the table carefully to determine if your IOS release contains these fixes. Most fixed releases for the TCP and SNMP advisories such as http://www.cisco.com/warp/public/707/cisco-sa-20040420-snmp.shtml and http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml contained the fixes for this BGP advisory. 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," "Interim," 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). When selecting a release, keep in mind the following definitions: Maintenance Most heavily tested, stable, and highly recommended release of a release train in any given row of the table. Rebuild Constructed from the previous maintenance or major release in the same train, it contains the fix for a specific defect. Although it receives less testing, it contains only the minimal changes necessary to repair the vulnerability. Interim Built at regular intervals between maintenance releases and receives less testing. Interims should be selected only if there is no other suitable release that addresses the vulnerability. Interim images should be upgraded to the next available maintenance release as soon as possible. Interim releases are not available through manufacturing, and usually they are not available for customer download from Cisco.com without prior arrangement with the Cisco TAC. In all cases, customers should exercise caution to confirm that the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new software release. If the information is not clear, contact the Cisco TAC for assistance as shown in the Obtaining Fixed Software section below. More information on Cisco IOS software release names and abbreviations is available at http://www.cisco.com/warp/public/620/1.html. The fixes will be available at the Software Center located at http://www.cisco.com/tacpage/sw-center/. For software installation and upgrade procedures, see http://www.cisco.com/warp/public/130/upgrade_index.shtml. For a current view of all posted and repaired images for Cisco IOS, please check the listing available to registered Cisco.com users at: http://www.cisco.com/tacpage/sw-center/sw-ios.shtml. +------------------------------------------------+ | Major | Availability of Repaired Releases | | Release | * | |------------+-----------------------------------| | Affected | | Interim | | | 11.1-Based | Rebuild | ** | Maintenance | | Release | | | | |------------+-----------------------------------| | 11.1 | Migrate to 11.2 or later | |------------+-----------------------------------| | 11.1AA | Migrate to 11.2P or later | |------------+-----------------------------------| | 11.1CA | Migrate to 12.0 or later | |------------+-----------------------------------| | 11.1CC | Migrate to 12.0 or later | |------------+-----------------------------------| | Affected | | Interim | | | 11.2-Based | Rebuild | ** | Maintenance | | Release | | | | |------------+-----------+---------+-------------| | 11.2 | 11.2(26g) | | | |------------+-----------+---------+-------------| | 11.2P | 11.2(26) | | | | | P7 | | | |------------+-----------------------------------| | 11.2SA | Not Vulnerable | |------------+-----------------------------------| | Affected | | Interim | | | 11.3-Based | Rebuild | ** | Maintenance | | Release | | | | |------------+-----------+---------+-------------| | 11.3 | 11.3(11f) | | | |------------+-----------+---------+-------------| | 11.3T | 11.3(11b) | | | | | T5 | | | |------------+-----------+---------+-------------| | Affected | | Interim | | | 12.0-Based | Rebuild | ** | Maintenance | | Release | | | | |------------+-----------+---------+-------------| | 12.0 | | | 12.0(27) | |------------+-----------------------------------| | 12.0DA | Migrate to 12.2DA or later | |------------+-----------------------------------| | | 12.0(21) | | | | | S7 | | | | |-----------+---------+-------------| | | 12.0(22) | | | | | S2e | | | | |-----------+---------+-------------| | | 12.0(22) | | | | | S3c | | | | |-----------+---------+-------------| | | 12.0(22) | | | | | S4a | | | | |-----------+---------+-------------| | 12.0S | 12.0(22) | | | | | S5 | | | | |-----------+---------+-------------| | | 12.0(23) | | | | | S3 | | | | |-----------+---------+-------------| | | 12.0(24) | | | | | S2 | | | | |-----------+---------+-------------| | | 12.0(25) | | | | | S1 | | | | |-----------+---------+-------------| | | | | 12.0(26)S | |------------+-----------------------------------| | 12.0SL | Migrate to 12.0(23)S3 or later | |------------+-----------------------------------| | | 12.0(17) | | | | | ST10 | | | | | Available | | | | | upon | | | | 12.0ST | request | | | | |-----------+---------+-------------| | | 12.0(21) | | | | | ST7 | | | | |-----------------------------------| | | Migrate to 12.0(26)S2 or later | |------------+-----------------------------------| | 12.0SV | | | 12.0(27)SV | |------------+-----------+---------+-------------| | 12.0SX | 12.0(25) | | | | | SX | | | |------------+-----------+---------+-------------| | | 12.0(23) | | | | | SZ3 | | | |12.0SZ |-----------+---------+-------------| | | | | 12.0(26)SZ | | |-----------------------------------| | | Migrate to 12.0(26)S2 or later | |------------+-----------------------------------| | 12.0T | Migrate to 12.1 or later | |------------+-----------------------------------| | | 12.0(16) | | | | | W5(21c) | | | | |-----------+---------+-------------| | | 12.0(25) | | | | | W5(27b) | | | |12.0W5 |-----------+---------+-------------| | | 12.0(26) | | | | | W5(28a) | | | | |-----------+---------+-------------| | | 12.0(27) | | | | | W5(29) | | | |------------+-----------------------------------| | 12.0WC | Not Vulnerable | |------------+-----------------------------------| | 12.0WX | Migrate to 12.0W5 or later | |------------+-----------------------------------| | 12.0XA | Migrate to 12.1 latest or later | |------------+-----------------------------------| | 12.0XC | Migrate to 12.1 latest or later | |------------+-----------------------------------| | 12.0XD | Migrate to 12.1 latest or later | |------------+-----------------------------------| | 12.0XE | Migrate to 12.1E latest or later | |------------+-----------------------------------| | 12.0XG | Migrate to 12.1 latest or later | |------------+-----------------------------------| | 12.0XH | Migrate to 12.1 latest or later | |------------+-----------------------------------| | 12.0XI | Migrate to 12.1 latest or later | |------------+-----------------------------------| | 12.0XJ | Migrate to 12.1 latest or later | |------------+-----------------------------------| | 12.0XK | Migrate to 12.1T latest or later | |------------+-----------------------------------| | 12.0XL | Migrate to 12.2 latest or later | |------------+-----------------------------------| | 12.0XN | Migrate to 12.1 latest or later | |------------+-----------------------------------| | 12.0XP | Not Vulnerable | |------------+-----------------------------------| | 12.0XR | Migrate to 12.2 latest or later | |------------+-----------------------------------| | 12.0XS | Migrate to 12.1E latest or later | |------------+-----------------------------------| | 12.0XU | Not Vulnerable | |------------+-----------------------------------| | Affected | | Interim | | | 12.1-Based | Rebuild | ** | Maintenance | | Release | | | | |------------+-----------+---------+-------------| | 12.1 | | | 12.1(20) | |------------+-----------------------------------| | 12.1AA | Migrate to 12.2 latest or later | |------------+-----------------------------------| | | Not Vulnerable | |12.1AX |-----------------------------------| | | 12.1AY | Not Vulnerable | |------------+-----------+-----------------------| | 12.1AZ | | | 12.1(14)AZ | |------------+-----------------------------------| | 12.1DA | Migrate to 12.2DA or later | |------------+-----------------------------------| | 12.1DB | Migrate to 12.2B or later | |------------+-----------------------------------| | | 12.1(6) | | | | | E12.0 | | | | |-----------+---------+-------------| | | 12.1(8b) | | | | | E14 | | | | |-----------+---------+-------------| | | 12.1(11b) | | | | | E12.0 | | | | |-----------+---------+-------------| | | 12.1(12c) | | | | 12.1E | E7 | | | | |-----------+---------+-------------| | | 12.1(13) | | | | | E6 | | | | |-----------+---------+-------------| | | 12.1(14) | | | | | E4 | | | | |-----------+---------+-------------| | | 12.1(19)E | | | | |-----------+---------+-------------| | | | | 12.1(20)E | |------------+-----------+---------+-------------| | 12.1EA | 12.1(14) | | | | | EA1 | | | |------------+-----------+---------+-------------| | 12.1EB | 12.1(14) | | | | | EB1 | | | |------------+-----------+---------+-------------| | 12.1EC | | | 12.1(19)EC | |------------+-----------+---------+-------------| | 12.1EO | | | 12.1(19)EO | |------------+-----------+---------+-------------| | 12.1EV | 12.1(12c) | | | | | EV2 | | | |------------+-----------+---------+-------------| | 12.1EW | | | 12.1(19)EW | |------------+-----------------------------------| | 12.1EX | Migrate to 12.1(14)E4 or later | |------------+-----------------------------------| | 12.1EY | Migrate to 12.1(14)E4 or later | |------------+-----------------------------------| | 12.1T | 12.1(5) | | | | | T19 | | | |------------+-----------------------------------| | 12.1XA | Migrate to 12.1(5)T19 or later | |------------+-----------------------------------| | 12.1XB | Migrate to 12.1(5)T19 or later | |------------+-----------------------------------| | 12.1XC | Migrate to 12.1(5)T19 or later | |------------+-----------------------------------| | 12.1XD | Migrate to 12.2 or later | |------------+-----------------------------------| | 12.1XE | Migrate to 12.1E latest or later | |------------+-----------------------------------| | 12.1XF | Migrate to 12.2(4)T6 or later | |------------+-----------------------------------| | 12.1XG | Migrate to 12.2(4)T6 or later | |------------+-----------------------------------| | 12.1XH | Migrate to 12.2 or later | |------------+-----------------------------------| | 12.1XI | Migrate to 12.2 latest or later | |------------+-----------------------------------| | 12.1XJ | Migrate to 12.2(4)T6 or later | |------------+-----------------------------------| | 12.1XL | Migrate to 12.2T latest or later | |------------+-----------------------------------| | 12.1XM | Migrate to 12.2T latest or later | |------------+-----------------------------------| | 12.1XP | Migrate to 12.2(4)T6 or later | |------------+-----------------------------------| | 12.1XQ | Migrate to 12.2T latest or later | |------------+-----------------------------------| | 12.1XR | Migrate to 12.2T latest or later | |------------+-----------------------------------| | 12.1XT | Migrate to 12.2(4)T6 or later | |------------+-----------------------------------| | 12.1XU | Migrate to 12.2T latest or later | |------------+-----------------------------------| | 12.1XV | Migrate to 12.2XB or later | |------------+-----------------------------------| | 12.1XY | Migrate to 12.2XB or later | |------------+-----------------------------------| | 12.1YA | Migrate to 12.2(8)T10 or later | |------------+-----------------------------------| | 12.1YB | Migrate to 12.2(4)T6 or later | |------------+-----------------------------------| | 12.1YC | Migrate to 12.2(8)T10 or later | |------------+-----------------------------------| | 12.1YD | Migrate to 12.2(8)T10 or later | |------------+-----------------------------------| | 12.1YH | Migrate to 12.2(13)T5 or later | |------------+-----------------------------------| | 12.1YJ | Not Vulnerable | |------------+-----------------------------------| | Affected | | Interim | | | 12.2-Based | Rebuild | ** | Maintenance | | Release | | | | |------------+-----------+---------+-------------| | | 12.2(10d) | | | | |-----------+---------+-------------| | | 12.2(12e) | | | | |-----------+---------+-------------| | | 12.2(12h) | | | | 12.2 | M1 | | | | |-----------+---------+-------------| | | 12.2(13c) | | | | |-----------+---------+-------------| | | 12.2(16a) | | | | |-----------+---------+-------------| | | | | 12.2(17) | |------------+-----------+---------+-------------| | 12.2B | 12.2(15) | | | | | B1 | | | |------------+-----------+---------+-------------| | 12.2BC | 12.2(15) | | | | | BC1 | | | |------------+-----------------------------------| | 12.2BW | Migrate to 12.2(15)T12 or later | |------------+-----------------------------------| | 12.2BX | | | 12.2(16)BX | |------------+-----------------------------------| | 12.2BY | Migrate to 12.2(15)B1 or later | |------------+-----------------------------------| | 12.2BZ | Migrate to 12.2(16)BX or later | |------------+-----------------------------------| | 12.2CX | | | 12.2(15)CX | |------------+-----------+---------+-------------| | 12.2DA | 12.2(12) | | | | | DA6 | | | |------------+-----------------------------------| | 12.2DD | Migrate to 12.2(15)B1 or later | |------------+-----------------------------------| | 12.2DX | Migrate to 12.2(15)B1 or later | |------------+-----------------------------------| | 12.2EW | | | 12.2(18)EW | |------------+-----------+---------+-------------| | 12.2JA | | | 12.2(13)JA | |------------+-----------+---------+-------------| | | 12.2(14) | | | | 12.2S | S2 | | | | |-----------+---------+-------------| | | | | 12.2(18)S | |------------+-----------+---------+-------------| | 12.2SE | | | 12.2(18)SE | |------------+-----------+---------+-------------| | 12.2SU | | | 12.2(14)SU | |------------+-----------+---------+-------------| | 12.2SV | | | 12.2(18)SV | |------------+-----------+---------+-------------| | 12.2SW | | | 12.2(18)SW | |------------+-----------+---------+-------------| | 12.2SX | 12.2(14) | | | | | SX2 | | | |------------+-----------+---------+-------------| | 12.2SXA | 12.2(17b) | | | | | SXA | | | |------------+-----------+---------+-------------| | 12.2SXB | 12.2(17d) | | | | | SXB | | | |------------+-----------+---------+-------------| | 12.2SY | | | 12.2(14)SY | |------------+-----------+---------+-------------| | 12.2SZ | 12.2(14) | | | | | SZ2 | | | |------------+-----------+---------+-------------| | | 12.2(4)T6 | | | | |-----------+---------+-------------| | | 12.2(8) | | | | | T10 | | | | |-----------+---------+-------------| | | 12.2(11) | | | | 12.2T | T9 | | | | |-----------+---------+-------------| | | 12.2(13) | | | | | T5 | | | | |-----------+---------+-------------| | | 12.2(15) | | | | | T4 | | | |------------+-----------------------------------| | 12.2XA | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XB | 12.2(2) | | | | | XB16 | | | |------------+-----------------------------------| | 12.2XD | Migrate to 12.2(8)T10 or later | |------------+-----------------------------------| | 12.2XE | Migrate to 12.2(8)T10 or later | |------------+-----------------------------------| | 12.2XG | Migrate to 12.2(8)T10 or later | |------------+-----------------------------------| | 12.2XH | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XI | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XJ | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XK | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XL | Migrate to 12.2(15)T4 or later | |------------+-----------------------------------| | 12.2XM | Migrate to 12.2(15)T4 or later | |------------+-----------------------------------| | 12.2XN | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XQ | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XS | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XT | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2XU | Migrate to 12.2(15)T12 or later | |------------+-----------------------------------| | 12.2XW | Migrate to 12.2(11)T9 or later | |------------+-----------------------------------| | 12.2YA | Migrate to 12.2(15)T4 or later | |------------+-----------------------------------| | 12.2YB | Migrate to 12.2(15)T4 or later | |------------+-----------------------------------| | 12.2YC | Migrate to 12.2(11)T11 or later | |------------+-----------------------------------| | 12.2YD | Migrate to 12.2(8)YY or later | |------------+-----------------------------------| | 12.2YE | Migrate to 12.2S or later | |------------+-----------------------------------| | 12.2YF | Migrate to 12.2(15)T4 or later | |------------+-----------------------------------| | 12.2YG | Migrate to 12.2(13)T5 or later | |------------+-----------------------------------| | 12.2YH | Migrate to 12.2(15)T4 or later | |------------+-----------------------------------| | 12.2YJ | Migrate to 12.2(15)T4 or later | |------------+-----------------------------------| | 12.2YL | Migrate to 12.3(2)T or later | |------------+-----------------------------------| | 12.2YM | Migrate to 12.3(2)T or later | |------------+-----------------------------------| | 12.2YN | Migrate to 12.3(2)T or later | |------------+-----------------------------------| | 12.2YO | Migrate to 12.2(14)SY or later | |------------+-----------------------------------| | 12.2YP | 12.2(11) | | | | | YP1 | | | |------------+-----------------------------------| | 12.2YQ | Migrate to 12.3(4)T or later | |------------+-----------------------------------| | 12.2YR | Migrate to 12.3(4)T or later | |------------+-----------------------------------| | 12.2YS | Migrate to 12.3T or later | |------------+-----------------------------------| | 12.2YT | Migrate to 12.2(15)T4 or later | |------------+-----------------------------------| | 12.2YU | Migrate to 12.3(4)T or later | |------------+-----------------------------------| | 12.2YV | Migrate to 12.3(4)T or later | |------------+-----------------------------------| | 12.2YW | Migrate to 12.3(2)T or later | |------------+-----------------------------------| | 12.2YX | Migrate to 12.2(14)SU or later | |------------+-----------------------------------| | 12.2YY | 12.2(8) | | | | | YY3 | | | |------------+-----------------------------------| | 12.2YZ | Migrate to 12.2(14)SZ or later | |------------+-----------------------------------| | 12.2ZA | 12.2(14) | | | | | ZA2 | | | |------------+-----------------------------------| | 12.2ZB | Migrate to 12.3T or later | |------------+-----------------------------------| | 12.2ZC | Migrate to 12.3T or later | |------------+-----------------------------------| | 12.2ZE | Migrate to 12.3 or later | |------------+-----------------------------------| | 12.2ZF | Migrate to 12.3(4)T or later | |------------+-----------------------------------| | 12.2ZG | Migrate to 12.3(4)T or later | |------------+-----------------------------------| | 12.2ZH | Migrate to 12.3(4)T or later | |------------+-----------------------------------| | 12.2ZI | Migrate to 12.2(18)S or later | |------------+-----------------------------------| | 12.2ZK | | | 12.2(15)ZK | |------------+-----------+---------+-------------| | 12.2ZL | | | 12.2(15)ZL | |------------+-----------------------------------| | 12.2ZN | Migrate to 12.3(2)T or later | |------------+-----------------------------------| | 12.2ZO | | | 12.2(15)ZO | |------------+-----------+---------+-------------| | 12.2ZP | | | 12.2(13)ZP | |------------+-----------+---------+-------------| | Affected | | Interim | | | 12.3-Based | Rebuild | ** | Maintenance | | Release | | | | |------------+-----------------------------------| | 12.3 | Not Vulnerable | |------------+-----------------------------------| | 12.3T | Not Vulnerable | +------------------------------------------------+ Obtaining Fixed Software ======================== 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/tacpage/sw-center. 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 assistance with the upgrade, which should be free of charge. 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 Please 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. Please do not contact either "psirt(a)cisco.com" or "security-alert(a)cisco.com" for software upgrades. See 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. 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. Workarounds =========== The effectiveness of any workaround 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 is the most appropriate for use in the intended network before it is deployed. For additional information regarding BGP security risk assessment, mitigation techniques, and deployment best practices, please consult ftp:// ftp-eng.cisco.com/cons/isp/security/BGP-Risk-Assesment-v.pdf. BGP MD5 Under normal circumstances, due to inherent security factors in the TCP protocol such as sequence number checks, it is difficult but possible to forge an appropriate packet to exploit this problem. Configuring your Cisco IOS device for BGP MD5 authentication is a valid workaround to protect the vulnerable device. This can be configured as shown in the following example: router(config)# router bgp router(config-router)# neighbor <IP_address> password <enter_your_secret_here> It is necessary to configure the same shared MD5 secret on both peers and at the same time. Failure to do so will break the existing BGP session and the new session will not get established until the exact same secret is configured on both devices. For a detailed discussion on how to configure BGP, refer to the following document: http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_configurati… Once the secret is configured, it is prudent to change it periodically. The exact period must fit within your company security policy but it should not be longer than a few months. When changing the secret, again it must be done at the same time on both devices. Failure to do so will break your existing BGP session. The exception is if your Cisco IOS software release contains the integrated CSCdx23494 fix on both sides of the connection. With this fix, the BGP session will not be terminated when the MD5 secret is changed only on one side. The BGP updates, however, will not be processed until either the same secret is configured on both devices or the secret is removed from both devices. Infrastructure Access Control Lists 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 white paper entitled "Protecting Your Core: Infrastructure Protection Access Control Lists" presents guidelines and recommended deployment techniques for infrastructure protection ACLs: http://www.cisco.com/warp/public/707/iacl.html Exploitation and Public Announcements ===================================== The research which led to this vulnerability being discovered was announced in a public announcement at NANOG in June 2003. The Cisco PSIRT team is not aware of any malicious use of the vulnerabilities described in this advisory. We were made aware of this issue through internal testing as well as notification from a research team at the University of California at Santa Barbara. The Cisco PSIRT is not aware of any malicious use of the vulnerability described in this advisory. Status of This Notice: FINAL ===================== This Advisory is provided on an "as is" basis and does not imply any kind of guarantee or warranty of any kind. Your use of the information on the Advisory or materials linked from the Advisory is at your own risk. Cisco reserves the right to change or update this notice at anytime. Distribution ============ This advisory will be posted on Cisco's worldwide website at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.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 (includes CERT/CC) * bugtraq(a)securityfocus.com * vulnwatch(a)wulnwatch.org * cisco(a)spot.colorado.edu * cisco-nsp(a)puck.nether.net * full-disclosure(a)lists.netsys.com * 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 ================ +---------------------------------------------+ | Revision | 16-June-2004 | Initial Public | | 1.0 | | 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/warp/public/707/sec_incident_response.shtml. 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-2004 Cisco Systems, Inc. All rights reserved. -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQA/AwUBQNBRC3sxqM8ytrWQEQLpGQCgiM8vHSFNW9SOGbvyOWN6qRvHWxAAn08R 66EU/1ILdWzJMUxjqJKBy1B2 =YmJU -----END PGP SIGNATURE-----

1 0

Yahoo Raises Stakes in E-Mail War with Google
by Henry Linneweh 16 Jun '04

16 Jun '04

This is what I was talking about... http://www.reuters.com/newsArticle.jhtml;jsessionid=ROKTUY2SVUOBMCRBAELCFFA…

2 1

Re: Math 011 (Re: "Default" Points on your Internet "Re: Re: Re:")
by Rob Nelson 16 Jun '04

16 Jun '04

>* I have an infected machine that pounds out attacks and exploits > at high speeds, hurting thousands of systems hourly. Would you > like it shut off? Probably. Do you not agree that this is > grounds for disco/throttling/proxy -- at least temporarily? Implementing bandwidth throttling or metering and capping your users is probably going to be one of the best ways to deal with this. Saying that 'this kind of traffic" isn't permissible is not going to cut it. What I think many people are trying to say is that it's just traffic - you're treating it as a black box passing through your network. If it's dented, has holes in it, or green crap is oozing out the bottom, you're allowed to discard it. You might even say "No" if there's a lot of black boxes per {$time interval}. You're just not able to look at it and say "Hey, you don't need that!" Now you've got ISP's making judgement calls on what traffic you actually want. This may be fine for mom and dad, but not for most people (yes, most people - including mom and pops who play an occassional game or use VoiP apps their kids installed). Plus, what happens when we start getting virus'es that use SSL/SSH to communicate? You're going to be SoL at determining packet contents at that point... Rob Nelson ronelson(a)vt.edu

1 0

Best Pratice for MAN security?
by Joe Shen 16 Jun '04

16 Jun '04

Hi, Is there any paper/document on best-pratice for MAN security? Is there a recommended version list for IOS or Juniper OS? thanks in advance joe ---- Msg sent via Spymac Mail - http://www.spymac.com

1 0

Akamai DNS Issue?
by Leo Bicknell 16 Jun '04

16 Jun '04

From here neither www.google.com, nor www.apple.com work. Both seem to return CNAMES to akadns.net addresses (eg, www.google.akadns.net, www.apple.com.akadns.net) and from here all of the akadns.net servers listed in whois are failing to respond. Can someone confirm from another location? Comments from Akamai? -- Leo Bicknell - bicknell(a)ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request(a)tmbg.org, www.tmbg.org

15 15

Re: Akamai DNS issue
by Joe Shen 16 Jun '04

16 Jun '04

Confirm here in China. mail.yahoo.com is not reachable. I met this problem with www.toshiba.com about a month before, when www.toshiba.com could only be resolved by using AT&T's DNS server cache. joe ---- Msg sent via Spymac Mail - http://www.spymac.com

1 0