Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Red Code Virus hits Some Cisco Modems, too
Message
 
À
02/08/2001 18:34:54
Nancy Folsom
Pixel Dust Industries
Washington, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00539135
Message ID:
00539222
Vues:
10
My Cisco 675 router took several Code Red hits. I could get it back for 5 or ten minutes before another scan would block it up. So, I logged into it with telnet and after getting pass the exec level and into the enable level I issued a "set web remote 10.0.0.1 enabled" command followed by 'write' and then 'quit"
Haven't had any problems since.
JLK

P.S. - I'm no genius, those are the steps recommened by Cisco!


>My Cisco 678 DSL modem is toast today after getting hit by the worm. That was unexpected. Might have thought QWest would have emailed security bulletins to their subscribers. Anyway...
>
>From http://www.cert.org/advisories/CA-2001-23.html:
>
>CERT® Advisory CA-2001-23 Continued Threat of the "Code Red" Worm
>Original release date: July 26, 2001
>Last revised: July 30, 2001
>Source: CERT/CC
>
>A complete revision history can be found at the end of this file.
>
>Systems Affected
>Microsoft Windows NT 4.0 with IIS 4.0 or IIS 5.0 enabled and Index Server 2.0 installed
>Windows 2000 with IIS 4.0 or IIS 5.0 enabled and Indexing services installed
>Cisco CallManager, Unity Server, uOne, ICS7750, Building Broadband Service Manager (these systems run IIS)
>Unpatched Cisco 600 series DSL routers
>
>Overview
>
>Since around July 13, 2001, at least two variants of the self-propagating malicious code "Code Red" have been attacking hosts on the Internet (see CA-2001-19 "Code Red" Worm Exploiting Buffer Overflow In IIS Indexing Service DLL). Different organizations who have analyzed "Code Red" have reached different conclusions about the behavior of infected machines when their system clocks roll over to the next month. Reports indicate that there are a number of systems with their clocks incorrectly set, so we believe the worm will begin propagating again on August 1, 2001 0:00 GMT. There is evidence that tens of thousands of systems are already infected or vulnerable to re-infection at that time. Because the worm propagates very quickly, it is likely that nearly all vulnerable systems will be compromised by August 2, 2001.
Nebraska Dept of Revenue
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform