- NANOG - lists.nanog.org

Problems with either Cisco.com or AT&T?
by Paul Ferguson 08 Aug '07

08 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No idea -- maybe just a hiccup? - From my office in San Jose: %traceroute www.cisco.com Tracing route to www.cisco.com [198.133.219.25] over a maximum of 30 hops: [snip] 7 3 ms 3 ms 3 ms so-3-0-0.mpr2.sjc7.us.above.net [64.125.30.173] 8 3 ms 3 ms 3 ms above-att.sjc7.us.above.net [64.125.13.50] 9 7 ms 7 ms 7 ms tbr1.sffca.ip.att.net [12.123.12.2] 10 6 ms 6 ms 6 ms gbr5.sffca.ip.att.net [12.122.11.74] 11 6 ms 6 ms 6 ms gar1.sj2ca.ip.att.net [12.122.2.253] 12 * * * Request timed out. 13 * * * Request timed out. 14 * ^C - From MIT: Tracing to: www.cisco.com 1 legacy26-0.default.csail.mit.edu (18.26.0.1) [AS3] 0 ms 0 ms 0 ms 2 kalgan.trantor.csail.mit.edu (128.30.0.245) [AS40] 0 ms 0 ms 0 ms 3 B24-RTR-2-CSAIL.MIT.EDU (18.4.7.1) [AS3] 0 ms 0 ms 0 ms 4 EXTERNAL-RTR-1-BACKBONE.MIT.EDU (18.168.0.18) [AS3] 1 ms 4 ms 2 ms 5 ge-6-23.car2.Boston1.Level3.net (4.79.2.1) [AS3356] 0 ms * 0 ms 6 * * ae-5-5.ebr1.NewYork1.Level3.net (4.69.132.250) [AS3356] 8 ms 7 ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) [AS3356] 10 ms 5 ms 16 ms 8 ae-13-69.car3.NewYork1.Level3.net (4.68.16.5) [AS3356] 67 ms 59 ms 58 ms 9 att-level3-oc192.NewYork1.Level3.net (4.68.127.150) [AS3356] 17 ms 127 ms 12 ms 10 tbr1.n54ny.ip.att.net (12.123.3.57) [] [MPLS: Label 31537 Exp 0] 80 ms 79 ms 79 ms 11 12.122.16.153 (12.122.16.153) [] [MPLS: Label 19 Exp 0] 76 ms 77 ms 77 ms 12 cr1.cgcil.ip.att.net (12.122.1.190) [] [MPLS: Label 1188 Exp 0] 77 ms 76 ms 77 ms 13 12.122.17.146 (12.122.17.146) [] [MPLS: Label 31051 Exp 0] 77 ms 78 ms 78 ms 14 tbr1.sffca.ip.att.net (12.122.10.6) [] [MPLS: Label 31320 Exp 0] 78 ms 78 ms 78 ms 15 gbr5.sffca.ip.att.net (12.122.11.74) [] [MPLS: Label 323 Exp 0] 72 ms 71 ms 71 ms 16 gar1.sj2ca.ip.att.net (12.122.2.253) [] 76 ms 76 ms 77 ms 17 * * * 18 * * * 19 * * * 20 * * * - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.6.2 (Build 2014) wj8DBQFGugixq1pz9mNUZTMRAnY3AKCIeE2oiRKl11ZRgsOLs/q6J5TyLwCgi/SQ mnTSn9TJY+yB2cjZSeKaulM= =DGbM -----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/

10 11

RE: Problems with either Cisco.com or AT&T?
by Michael Airhart 08 Aug '07

08 Aug '07

I can't speak for Cisco or Cisco IT, but as evidenced by this email, at least part of our connectivity is up. No doubt someone official is looking at it as we speak. (I'll just lurk Nanog to get the skinny).. >A brief look at routeviews shows www.cisco.com (198.133.219.25) >originating from AS109 (Cisco) and transiting via AS7132 (AT&T/SBC) and >AS7018 (AT&T). Thus I suspect this is an issue with AS109 (Cisco) and >not with their providers. Though, I do feel wrong using the plural >"providers" in this case... > >-Benson > >

2 1

weight vs. volume (95th percentile vs transfer in M/Gbytes)
by Jim Mercer 08 Aug '07

08 Aug '07

over the years, i've grown quite accustomed to feeling out pricing of bandwidth based on 95th percentile peak utilization with various minimums and potential tiers. i've always sorta viewed pricing by "bytes transferred" to be a consumer thing that my uncle might pay when hosting his webpages showing his matchbox collection. now i'm faced with a jurisdiction where the only providers (all 2 of them) will only give pricing in "bytes transferred". they are not interested in giving me pricing based on 95th percentile, and as such i'm having a tough time budgetting for some of my applications. (pisses me off because i'm sure _they_ are paying by 995th percentile) with 95th percentile, i could always trottle down the applications or figure out what my estimated `overage might be. has anyone got a formula for comparing 95th percentile billing with bytes transferred? -- Jim Mercer jim(a)reptiles.org +971 55 410-5633 "I'm Prime Minister of Canada, I live here and I'm going to take a leak." - Lester Pearson in 1967, during a meeting between himself and President Lyndon Johnson, whose Secret Service detail had taken over Pearson's cottage retreat. At one point, a Johnson guard asked Pearson, "Who are you and where are you going?"

3 2

SBC Issues/Contact?
by Koch, Christian 08 Aug '07

08 Aug '07

Anyone have a contact for sbc? They are preventing me from getting to cisco.com P:\>tracert cisco.com Tracing route to cisco.com [198.133.219.25] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.5.7.254 2 <1 ms <1 ms <1 ms 209.10.21.253 3 28 ms 28 ms 28 ms 209.10.9.37 4 28 ms 27 ms 27 ms 209.10.9.25 5 28 ms 27 ms 27 ms g-1-0-0.core2.nyc15.qualitytech.com [209.10.10.186] 6 28 ms 28 ms 28 ms so-1-0-0.core1.cgx2.globix.net [209.10.10.161] 7 28 ms 28 ms 28 ms pos-2-0.peer1.cgx3.globix.net [209.10.12.82] 8 451 ms 455 ms 450 ms ex1-g1-0.eqchil.sbcglobal.net [206.223.119.79] 9 513 ms 499 ms 501 ms ded4-g8-3-0.sntc01.pbi.net [151.164.41.165] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * *

2 3

Cisco Security Advisory: Cisco IOS Secure Copy Authorization Bypass Vulnerability
by Cisco Systems Product Security Incident Response Team 08 Aug '07

08 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cisco Security Advisory: Cisco IOS Secure Copy Authorization Bypass Vulnerability Advisory ID: cisco-sa-20070808-scp http://www.cisco.com/warp/public/707/cisco-sa-20070808-scp.shtml Revision 1.0 For Public Release 2007 August 08 1600 UTC (GMT) - ----------------------------------------------------------------------- Summary ======= The server side of the Secure Copy (SCP) implementation in Cisco Internetwork Operating System (IOS) contains a vulnerability that allows any valid user, regardless of privilege level, to transfer files to and from an IOS device that is configured to be a Secure Copy server. This vulnerability could allow valid users to retrieve or write to any file on the device's filesystem, including the device's saved configuration. This configuration file may include passwords or other sensitive information. The IOS Secure Copy Server is an optional service that is disabled by default. Devices that are not specifically configured to enable the IOS Secure Copy Server service are not affected by this vulnerability. This vulnerability does not apply to the IOS Secure Copy Client feature. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-scp.shtml. Note: The August 08, 2007 publication includes four Security Advisories and one Security Response. The advisories all affect IOS, one additionally affects Cisco Unified Communications Manager as well. Each advisory lists the releases that correct the vulnerability described in the advisory, and the advisories also detail the releases that correct the vulnerabilities in all four advisories. Individual publication links are listed below: * Cisco IOS Information Leakage Using IPv6 Routing Header http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-IPv6-leak.shtml * Cisco IOS Next Hop Resolution Protocol Vulnerability http://www.cisco.com/warp/public/707/cisco-sa-20070808-nhrp.shtml * Cisco IOS Secure Copy Authorization Bypass Vulnerability http://www.cisco.com/warp/public/707/cisco-sa-20070808-scp.shtml * Voice Vulnerabilities in Cisco IOS and Cisco Unified Communications Manager http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml * Cisco Unified MeetingPlace XSS Vulnerability http://www.cisco.com/warp/public/707/cisco-sr-20070808-mp.shtml Affected Products ================= Vulnerable Products +------------------ Cisco devices running certain 12.2-based IOS releases and configured to offer Secure Copy server functionality are affected by this issue. A device running a vulnerable Cisco IOS 12.2-based is affected if the following command is present in the device configuration: ip scp server enable The IOS Secure Copy server is disabled by default. The Secure Copy server functionality is only available on encryption-capable images. Devices that do not run an encryption-capable images, which contain either k8 or k9 in the image name, are not vulnerable. If a device is running an encryption-capable image, the existence of the "ip scp server enable" command in the configuration will determine whether the device is affected. Please consult the table of fixed software in the Software Version and Fixes section for the specific 12.2-based IOS releases that are affected. 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". The image name will be displayed between parentheses on the next line of output followed by "Version" and 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.2(18)SXF10: Cisco Internetwork Operating System Software IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9-M), Version 12.2(18)SXF10, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2007 by cisco Systems, Inc. Compiled Fri 13-Jul-07 08:32 by kellythw Additional information about Cisco IOS release naming is available at http://www.cisco.com/warp/public/620/1.html. Products Confirmed Not Vulnerable +-------------------------------- Cisco devices that do not run IOS are not affected. Cisco IOS devices that do not have the Secure Copy server feature enabled are not affected. The following IOS release trains are not affected: * 12.0-based releases * 12.1-based releases * 12.3-based releases * 12.4-based releases Cisco IOS XR is not affected. No other Cisco devices are known to be affected. Details ======= Secure Copy (SCP) is a protocol similar to the Remote Copy (RCP) protocol, which allows for the transfer of files between systems. The main difference between SCP and RCP is that in SCP, all aspects of the file transfer session, including authentication, occur in encrypted form, which makes SCP a more secure alternative than RCP. SCP relies on the Secure Shell (SSH) protocol, which uses TCP port 22 by default. The server side of the Secure Copy implementation in Cisco IOS contains a vulnerability that allows any valid user, regardless of privilege level, to transfer files to and from an IOS device that is configured to be a Secure Copy server. This vulnerability could allow valid users to retrieve or write to any file on the device's filesystem, including the device's saved configuration. This configuration file may include passwords or other sensitive information. This vulnerability does not allow for authentication bypass; login credentials are verified and access is only granted if a valid username and password is provided. This vulnerability may cause authorization to be bypassed. A device with the Secure Copy server enabled is vulnerable regardless of whether Authentication, Authorization, and Accounting (AAA) is enabled. If access control is enabled on the Virtual Terminal (vty) via the "login" command, which allows logins via Virtual Terminals, then the device is affected. This vulnerability is documented in Cisco Bug ID CSCsc19259. Vulnerability Scoring Details +---------------------------- Cisco is providing scores for the vulnerabilities in this advisory based on the Common Vulnerability Scoring System (CVSS). The CVSS scoring in this Security Advisory is done in accordance with CVSS version 1.0. 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. CSCsc19259 - "All privilege level users can SCP running config" CVSS Base Score - 6.0 Access Vector - Remote Access Complexity - Low Authentication - Required Confidentiality Impact - Complete Integrity Impact - Complete Availability Impact - Complete Impact Bias - Normal CVSS Temporal Score - 5.0 Exploitability - Functional Remediation Level - Official-Fix Report Confidence - Confirmed Impact ====== Successful exploitation of the vulnerability described in this advisory may allow valid but unauthorized users to retrieve or write to any file on the device's filesystem, including the device's saved configuration. This configuration file may include passwords or other sensitive information. Software Versions 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) names a Cisco IOS release train. If a given release train is vulnerable, then the earliest possible releases that contain the fix (along with the anticipated date of availability for each, if applicable) are listed in the "First Fixed Release" column of the table. The "Recommended Release" column indicates the releases which have fixes for all the published vulnerabilities at the time of this Advisory. A device running a release in the given train that is earlier than the release in a specific column (less than the First Fixed Release) is known to be vulnerable. Cisco recommends upgrading to a release equal to or later than the release in the "Recommended Releases" column of the table. For further information about how Cisco IOS is built, numbered and maintained, please see the following URL: http://www.cisco.com/warp/public/620/1.html +-------------------------------------------------------------+ | Major | Availability of Repaired Releases | | Release | | |--------------+----------------------------------------------| | Affected | | Recommended | | 12.0-Based | First Fixed Release | Release | | Release | | | |-------------------------------------------------------------| | There are no affected 12.0 based releases | |-------------------------------------------------------------| | Affected | | Recommended | | 12.1-Based | First Fixed Release | Release | | Release | | | |-------------------------------------------------------------| | There are no affected 12.1 based releases | |-------------------------------------------------------------| | Affected | | Recommended | | 12.2-Based | First Fixed Release | Release | | Release | | | |--------------+----------------------------+-----------------| | 12.2 | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2B | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2BC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2BW | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2BY | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2BZ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2CX | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2CY | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2CZ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2DA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2DD | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2DX | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2EU | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2EW | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2EWA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2EX | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2EY | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2EZ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2FX | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2FY | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2FZ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2IXA | Vulnerable; first fixed in | 12.2(18)IXD1 | | | 12.2(18)IXD1 | | |--------------+----------------------------+-----------------| | 12.2IXB | Vulnerable; first fixed in | 12.2(18)IXD1 | | | 12.2(18)IXD1 | | |--------------+----------------------------+-----------------| | 12.2IXC | Vulnerable; first fixed in | 12.2(18)IXD1 | | | 12.2(18)IXD1 | | |--------------+----------------------------+-----------------| | 12.2IXD | 12.2(18)IXD1 | 12.2(18)IXD1 | |--------------+----------------------------+-----------------| | 12.2JA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2JK | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2MB | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2MC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2S | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SB | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SBC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SE | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SEA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SEB | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SEC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SED | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SEE | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SEF | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SEG | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SG | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SGA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SL | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SM | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SO | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SRA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SRB | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SU | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SV | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SVA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SVC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SW | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SX | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SXA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SXB | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SXD | Vulnerable; contact TAC | | |--------------+----------------------------+-----------------| | 12.2SXE | Vulnerable; first fixed in | 12.2(18)SXF10 | | | 12.2(18)SXF9 | | |--------------+----------------------------+-----------------| | 12.2SXF | 12.2(18)SXF9 | 12.2(18)SXF10 | |--------------+----------------------------+-----------------| | 12.2SXH | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SY | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2SZ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2T | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2TPC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2UZ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2VZ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XB | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XD | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XE | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XF | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XG | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XH | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XI | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XJ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XK | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XL | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XM | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XN | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XQ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XR | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XS | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XT | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XU | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XV | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2XW | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YB | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YD | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YE | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YF | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YG | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YH | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YJ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YK | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YL | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YM | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YN | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YO | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YP | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YQ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YR | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YS | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YT | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YU | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YV | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YW | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YX | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YY | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2YZ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZA | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZB | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZC | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZD | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZE | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZF | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZG | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZH | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZJ | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZL | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZP | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZR | Not Vulnerable | | |--------------+----------------------------+-----------------| | | Vulnerable; first fixed in | 12.2(33)SXH; | | 12.2ZU | 12.2(33)SXH available | available | | | 31-Aug-07 | 31-Aug-07 | |--------------+----------------------------+-----------------| | 12.2ZW | Not Vulnerable | | |--------------+----------------------------+-----------------| | 12.2ZY | Not Vulnerable | | |--------------+----------------------------+-----------------| | Affected | | Recommended | | 12.3-Based | First Fixed Release | Release | | Release | | | |-------------------------------------------------------------| | There are no affected 12.3 based releases | |-------------------------------------------------------------| | Affected | | Recommended | | 12.4-Based | First Fixed Release | Release | | Release | | | |-------------------------------------------------------------| | There are no affected 12.4 based releases | +-------------------------------------------------------------+ Workarounds =========== If the IOS Secure Copy Server functionality is not needed then the vulnerability described in this document can be mitigated by disabling the Secure Copy server. The Secure Copy server can be disabled by executing the following command in global configuration mode: no ip scp server enable If the Secure Copy server cannot be disabled due to operational concerns, then no workarounds exist. The risk posed by this vulnerability can be mitigated by following the best practices detailed in "Improving Security on Cisco Routers" at http://www.cisco.com/warp/public/707/21.html. Please refer to the Obtaining Fixed Software section for appropriate solutions to resolve this vulnerability. Due to the nature of this vulnerability, networking best practices like access control lists (ACLs) and Control Plane Policing (CoPP) that restrict access to a device to certain IP addresses or subnetworks may not be effective. If access is already granted to a specific IP address or subnetwork, a user with low privileges will be able to establish a Secure Copy session with the device, which would allow the user to exploit this vulnerability. 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 reported to Cisco by Vijay Sarvepalli from University of North Carolina at Greensboro. 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-20070808-scp.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 ================ +-------------------------------------------------------------+ | Revision 1.0 | 2007-August-08 | 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 2006-2007 Cisco Systems, Inc. All rights reserved. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGue/j8NUAbBmDaxQRAuIUAJ939GMmu2rcdLrhLxGg2an9qEPflwCeNsUe S1hoh9YafurxjagH1iUeZNY= =MHN2 -----END PGP SIGNATURE-----

1 0

bandwidth for PyCon 08 in Chicago
by Carl Karsten 08 Aug '07

08 Aug '07

Let me start with: I pretty much have no clue. but it is ok, because I don't get to spend any money. But I do get to help figure out how to get internet bandwidth to a hotel near Chicago (Crown in Rosemont) for a week in March 08 and figured maybe someone here can help. There are 2 aspects to this: 1. bandwidth for PyCon, and no one else. This is the easiest, but most costly. (20k ish total) 2. help the Crown upgrade their setup from 3 T1s to a DS3. (the fiber is there.) so they have it for other conventions. more hassle, more money, but less cost to PyCon. Below are some 'details' that a PyCon guy has collected. Anyone here feel this is there line of work? Carl K Highlights from Sean Reifschneider posts: -- begin quote -- 04/02/07 I've gotten a quote from Time Warner, one of the providers we use at our hosting facility. Their price would be $5,543/month with $750 setup for month-to-month DS-3 service. This would be a fully DS-3 running at 45mbps. On top of this, we would probably need to spend a couple of grand on a router to terminate the line. So far, this is the only place I've gotten who is willing to do a month-to-month DS-3, this pricing is quite good *** 4/8/07 Here are my preliminary numbers for networking for 2008 and 2009: 45mbps DS-3 for 2008: $6,300 45mbps DS-3 for 2009: $6,300 Router to terminate DS-3 for 2008&9: $4600 Additional access points for 2008&9: $2300 Switches, network, and power cables 2008&9: $500 Stands or mounting for APs for 2008&9: $1000 This largely assumes we are going to go with the DS-3, so things may change depending on that. The first year outlay would be around $14,700, second year I would expect to be more like $6,300. **** I did see one price saying $1300/month for a DS-3 with 10mbps, and 130mbps above that. This is burstable service, up to 45mbps, so we would just pay for what we'd use above 10mbps. *** 06/28/07 I believe the cost is something around $2500 for a single month term *** 7/7/07 I've asked Randy of TWTC what needs to be done about getting the contract signed for 2008. I've asked him to work with you, David, about the date and any other information he needs for the contrac -- end quote --

5 6

Re: large organization nameservers sending icmp packets to dns servers.
by Jason J. W. Williams 07 Aug '07

07 Aug '07

Hi Donald, I'm not prepared to call it stupid, but you're right it can cause issues. -J -------------------- Sent via BlackBerry ----- Original Message ----- From: Donald Stahl <don(a)calis.blacksun.org> To: Jason J. W. Williams Cc: Valdis.Kletnieks(a)vt.edu <Valdis.Kletnieks(a)vt.edu>; John Levine <johnl(a)iecc.com>; nanog(a)nanog.org <nanog(a)nanog.org> Sent: Tue Aug 07 12:14:11 2007 Subject: RE: large organization nameservers sending icmp packets to dns servers. > All things being equal (which they're usually not) you could use the ACK > response time of the TCP handshake if they've got TCP DNS resolution > available. Though again most don't for security reasons... Then most are incredibly stupid. Several anti DoS utilities force unknown hosts to initiate a query via TCP in order to be whitelisted. If the host can't perform a TCP query then they get blacklisted. In addition, any UDP truncated response needs to be retried via TCP- blocking it would cause a variety of problems. -Don !SIG:46b8b686156533728213125!

1 0

What's up at NTL/VirginMedia?
by Alexander Harrowell 07 Aug '07

07 Aug '07

Seems to be a large-scale outage going on at Virgin Media ex-NTL, AS5089 in the UK. Lost service about 1600GMT yesterday to a wide range of locations throughout the country. Recorded phone message now saying several post code areas in SW London suburbs still dark, but status page shows lots'o'tickets open all over the country. Anyone know what's up?

1 0

small correction Re: Content Delivery Networks
by Scott Weeks 07 Aug '07

07 Aug '07

--- patrick(a)ianai.net wrote: From: "Patrick W. Gilmore" <patrick(a)ianai.net> : While Level 3 (who owns Digital Island, which they : bought from Savvis, who got that when they : acquired Exodus, who bought way DI back when) A clarification, just for a historical note and fun. Hello former DI peeps out there! :-) Digital Island got the Footprint CDN when we acquired Sandpiper Networks for ~$600m back in 1999. Also, Exodus (back then known as the Evil Empire to many DI folks) never acquired DI. The Cable and Wireless US Division acquired both DI and Exodus, renamed everything to "Cable and Wireless America", performed the largest mass destruction of value many of us have ever seen (I believe over a billion dollars) and then went into bankruptcy. Then Savvis bought the Footprint part. Finally, Level 3 bought Footprint from Savvis. I believe this is everything... Ahhh, the bad 'ol days... >;-) scott --- patrick(a)ianai.net wrote: From: "Patrick W. Gilmore" <patrick(a)ianai.net> To: nanog(a)merit.edu Cc: "Patrick W. Gilmore" <patrick(a)ianai.net> Subject: Re: Content Delivery Networks Date: Mon, 6 Aug 2007 20:08:06 -0400 On Aug 6, 2007, at 5:10 PM, Rod Beck wrote: > Can anyone give a breakdown of the different kinds of content > deliver networks? For example, we have Akamai, which appears to be > a pure Layer 3 network that is tailored to pushing relatively small > files like web pages and we have Lime Light Networks, which is a > mix of Layer 1 and Layer 3, that focuses on bigger files like video > streams. I am not sure why you would say Akamai is "tailored to pushing relatively small files", since I do not believe they say that anywhere. LLNW does say they are focused on larger files. (I believe LLNW claims Akamai is focused on smaller files, but do you believe what Akamai says about LLNW?) I can confirm that Akamai does not have a backbone. Neither does Panther Express, CacheFly, or Mirror Image. While Level 3 (who owns Digital Island, which they bought from Savvis, who got that when they acquired Exodus, who bought way DI back when), LLNW, and at&t all have their own backbones. > Any insights out there? And what are the major challenges in making > scalable content delivery networks? Myriad. Some are hard to overcome, some are very hard. Keyword here being "scalable" - which you failed to define. What is "scalable" to you? 100 Gbps? 500 Gbps? The latter is medium-hard in the US, the former is nearly impossible in South Africa. Which brings us to geography. Are you US-centric? European? Asian? Six continents? Just a few specific countries? Plus, as you mention above, there's file size. How about streaming vs. HTTP? Optimize for latency or throughput? Did I mention cost? Etc., etc. If someone asked "what are the major challenges in making scalable backbones?", how would you answer? -- TTFN, patrick

1 0

Re: large organization nameservers sending icmp packets to dns servers.
by Valdis.Kletnieks＠vt.edu 07 Aug '07

07 Aug '07

On Mon, 06 Aug 2007 16:11:36 EDT, Matthew Crocker said: > But you could, it isn't hard to dump a BGP view into a box from a > border router and use that map to determine the proper DNS records to > return. It's harder than it looks, given the number of people who pop up on this list and ask how to get BGP to Do The Right Thing when 2 paths are the same length but vastly differing in bandwidth, number-of-actual-hops, and/or latency....

2 1