Slashdot Mirror
Code Red Worm Spreading, Set To Flood Whitehouse
Slow Internet service due to all those extra packets of malice may not be the worst effect: As sp1n writes: "It appears that due to the way the worm formats its HTTP request and the semi-random way it seeks out vulnerable systems, it is also causing Cisco 67x DSL routers, widely deployed by Qwest, using firmware prior to 2.4.1, as well as some others, such as 3Com LanModems, to crash -- recoverable only by a power cycle. I have yet to see any news outlet cover the affect this is having on DSL service. Qwest's Interprise networking department confirmed they are receiving reports from all 14 states in their territory. Some routers running pre-2.4.1 firmware are crashing even though the web admin is disabled. This has become a huge support nightmare for every ISP in the region."
Which begs the question -- is it "right" to create a sploit that connects back to the attacking machines and "patches" their system so that it is fixed.
It's a conspiracy. Everyone will hit the whitehouse.gov site to see if the alleged worm affected it, and in doing so, we have all been duped into participating in a DDoS attack on the site. Rather clever, actually. Proclaim the effect to create the cause.
Yep, I got a lot of them on both my cable modem box and my server.
/var/www/group/logs/access_log | wc -l
/var/www/otg/logs/access_log | wc -l
On the server:
[root@nova logs]# grep NNNNNNNNNN access_log | wc -l
34
[root@nova logs]# grep NNNNNNNNNN jes*access_log | wc -l
18
[root@nova logs]# grep NNNNNNNNNN trav*access_log | wc -l
20
[root@nova logs]# grep NNNNNNNNNN
18
[root@nova logs]# grep NNNNNNNNNN
19
---
Cool! Thanks for the info. A grep through my own logs showed a lot of similar traffic. Time to start the whois' on those ips!
... on a potential future target, if you ask me.
Be interesting to hear the analyses about this one when it's all over.
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
Count me in.
We should take a lot of weed with us.
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
bah-dumpsh!
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
Speak for yourself.
I'm using hash oil for fule in *my* tent!
Pollution never looked so sweet.
But seriously: where do we start? I wanna get off this chunk of rock. It hurts my ass.
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
Almost any integer, eh?
None of my int's are good enough.
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
http://www.qwest.com/dsl/customerservice/csco675up s.html
p s.html
http://www.qwest.com/dsl/customerservice/csco678u
Sounds great, but no BBQ in the space station.
*cough
Whoa - just checked the logs on my humble linux box (behind a cable modem) and I've had about 25 hits on 'default.ida' today. Looks like a unique IP every time.
Jeez, if this is coming to my obscure neck of the woods... gonna be a hell of a night for W's IT staff...
hmm... could these dialup victims be using Win98's 'Personal Web Server'? It's just IIS 3.x.
Wonder if that's vulnerable.
I noticed this yesterday in my logs as well as some other strange requests that looked like somebody trying to break in.
Say, here's an idea... machines which request URLs like this have already been cracked and may still be vulnerable to the hole that the worm exploits (or does the worm patch this hole after exploiting it?). Somebody could take control of the cracked machines in the same way that the worm did and once inside introduce an antidote that eliminates the worm and patches the vulnerability. This could even be set up as a cgi script so that these cracked machines can be automatically cured.
It's a nice thought, but probably not worth the effort. Somebody would be bound to get upset by this good samaritan hacking and sue. It would also be too tempting to have the IIS "patch" that the antidote delivers be Apache (and OpenBSD for the ambitious).
-----
Free P2P Backup, Windows & Linux
last night I experienced a similar problem on my machine. Someone had been using various proxies to proxy through my machine to various pay for click type sites. I quickly put an end to this by commenting out modproxy in my apache config. Whether this is related I don't know. One thing is for sure though. the rise of lame people is happing at an exponential rate. It will only continue to get worse from here. :\
-Moose
well, well, I just checked my logs. I have been scanned by lamers for this heh.
/default.ida?NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN%u9090%u6858% ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u6858%uc bd3%u7801%u9090%u9090%u8190%u00c3%u0003%u8b00%u531 b%u53ff%u0078%u0000%u00=a HTTP/1.0" 404 273
This showed up in my logs. I'm pasting it unadulterated seeing as I've found like 20 copies of it anyways so the script kiddies already have it.
207.68.188.44 - - [19/Jul/2001:15:15:30 -0400] "GET
How many of those who check whitehouse.gov to see if it's down will then check to see if they can get there through dot org or dot com, and think that what's at dot com is a "hacked" version of the dot gov?
I see even classic Slashdot is now pretty much unusable on dial up anymore.
Be sure to check out the inaugural address link.
I see even classic Slashdot is now pretty much unusable on dial up anymore.
'Course I'm not browsing whitehouse.gov at -1.
I see even classic Slashdot is now pretty much unusable on dial up anymore.
Probably windowsupdate is run on a server farm - one server was hacked, and when you hit refresh the load balancer sent you to another server that wasn't.
:)
Or maybe you were just unlucky
what versions of cbos does this affect? i was thinking of upgrading mine to 2.4.1 a few days ago... now might be a good time to do it.
---
and msft called linux anti-american!
---
Actually, you can do what you say only on a NT 4 IIS (default) installation: there the IIS runs as SYSTEM and can modify files. ;-) the IIS runs as a user that can't "patch" itself or overwrite "interesting" system files.
On 2000 and on system where some non-stupid admin did the initial installation (but not maintenance
Ciao,
Rob!
AniToolBox! An Open Source animation program!
This site lets you search for MS patches by product name and applied service pack. A hellava improvement over Microsoft's previous patch search.
Two words of warning:
1) W2K SP2, like all SPs, did not include all of the previous hotfixes. You might need to reapply some after applying the service pack. I think this particular exploit is one of those.
2) For W2K, you need to search under both "Windows 2000" and "IIS 5.0" to get all the patches.
Happy hunting!
--
Business. Numbers. Money. People. Computer World.
The stuff they say about certain HP printers is true too. We have a HP LaserJet 4000N, and it's been going down all day. The secretary (who's since gone home) has been confused as all else as to why the printer keeps giving some strange error. I'd guess that all HP's that use the same internal network spooler will have the same problem.
Here is the hall of shame of IP's from my Apache logs:
:-)
66.80.40.178
202.30.107.77
134.155.40.49
195.65.218.213
206.153.53.106
66.121.57.63
132.178.148.167
131.174.228.6
24.91.116.188
200.202.120.59
62.48.11.31
24.214.66.226
208.11.51.150
63.194.235.102
208.139.198.171
62.17.151.141
195.85.182.18
211.53.214.76
If your IP is on that list, you might want to patch it... Or better yet, switch to Linux and Apache...
Actually, 4pm PST is 12am GMT. PST is GMT-8. Mountain Standard is GMT-7.
--
--
"Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
That is irrelevant. PST was what was referenced, and is the subject of this thread, not PDT.
--
--
"Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
Tempting, but I block cookies whenever I can. If you bring some beer and steak, I'm there.
Visit me on #weirdness on the Galaxynet.
Can you interfere worms such as this by changing system/software clocks? Could a crafty craker proggy writer create some kind of independent time record to avoid such tampering affecting his effects?
Damn, I went from one every hour to about one every 10 minutes ... this is definitely hitting alot of folks since I have a DSL line with a pretty much unknown webserver.
/default.ida?NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN%u9090%u6858% ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u6858%uc bd3%u7801%u9090%u9090%u8190%u00c3%u0003%u8b00%u531 b%u53ff%u0078%u0000%u00=a HTTP/1.0" 400 252 "-" "-"
... http://news.cnet.com/news/0-1003-200-6617292.html
... http://slashdot.org/article.pl?sid=01/07/19/223024 6&mode=thread
l t. asp?url=/technet/security/bulletin/MS01-033.asp
I'm sending the following form letter to webmaster@, administrator@ and root@ of the reversed domain for anyone who I see sending me the request:
--------------
I noticed in my web server logs that your server tried to access a false web page today. This access is a signature of attacks coming from the Red Tape worm and it would appear you have an IIS server that is infected. The infected server (yours) then tries to contact other ISS servers to infect, generating the following request (the first IP address is the server that you have that is infected, though you may have many others with the same predicament):
[replace with the actual request]
###.###.###.### - - [19/Jul/2001:18:11:07 -0500] "GET
NOTE: If this is a dynamic IP address and you are an ISP, the above request should be able to help you track down your customer and help them fix this issue.
I'm only providing this note as a warning so that you can try and patch your machine. My web server was immune to this attack, so I was not directly affected.
For more details about this worm, please see the following sites:
News.com
Slashdot.org
To patch your server you should:
1) make sure you have all of the most recent service packs installed
2) make sure you have all of the available critical updates installed
3) install this patch:
http://www.microsoft.com/technet/treeview/defau
4) reboot
NOTE: I do not have a Windows IIS webserver with which to verify the above instructions, so I can't guarantee it will work, but the above practices should be done on a regular basis (if they had been done, including installing the patch mentioned, your web server would not have been compromised to begin with).
--------------
It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
This is acutally the "Press DOS attack." You get some security expert to claim that a worm is spreading all over the internet and will attack X site at 5pm. Then everyone who reads the story will go see if the site is down at 5pm. And of course since everyone is hitting reload to see when it is down, the site gets flooded and goes down while the virus/worm never exsisted!
-- Virtual Windows Project
I thought the analysis said the worm references the .91 address. DNS right now resolves to the .92 address. So no problem.
Cnet now says 100,000 servers infected.
At my company (small midwest ISP), I could feel the effects at around 10am CDT. A couple servers run by customers were infected and were sending out a *constant* stream of requests to random servers trying to infect others.
Oof.
FOR THE LOVE OF GOD, FIND GET YOUR Tee Ball at the White House INFORMATION BEFORE IT'S TOO LATE!!!
Karma: Excer..ex...excellahhh...realll good (mostly affected by drinking not done in moderation)
root.exe was left from the solaris worm that went around about a month and half ago. You guys have been hacked for a while. Scan your logs for entries that have "cmd.exe" in them and you'll find when you first got smacked.
I can't imagine that they didn't think as hard about security as Apache or Linux for example.
i'm not bashing microsoft here, but the windows3.1/95/98/nt/etc os's originated from dos which is a single user operating system. there were no concerns made with respect to security when dos was originally placed on the market. because of the application base dos had the various windowsxxx's that have come along had to be backwards compatable with dos programs. as a result you have this pseudomultiuser platform that implements security as an afterthought. see for example this article about windows xp.
on the other hand linux is based on unix, which microsoft trashes for being 30 year old technology, but this technology has had 30 years to iron out alot of the security issues. unix was also designed with multiple users in mind which affects everything from file access to memory allocation.
so in essance linux, via unix, has had alot more thought put into security than microsoft. as a result of linux being open alot of the security issues can be addressed by its users. because microsoft is closed the poor iis administrators have to sitback while their boxen are DOS'ed and wait for a patch to arrive. its sad really.
use LaTeX? want an online reference manager that
-- john
If you're router/firewall's linux, you can do this:
/sbin/route add -host 198.137.240.92 gw 127.0.0.1 dev lo
That will dump all of that traffic into space, and it will never hit your outbound ethernet card.
I presume similar things are possible on just about every piece of routing hardware out there.
--
Aaron Sherman (ajs@ajs.com)
I've got the same thing in my Apache access logs.. 17 unique hosts sent it. Haven't noticed any side effects or problems on Apache or Linux yet (I know this is an IIS worm, but it's best to be cautious).
It does show up how many people cannot be bothered to set up reverse DNS though. THe only likely problem is wastage of bandwidth.
So THAT's what it is.. Starting around 3 hours ago, my home desktop machine has been getting about 50 of those. One very 3 minutes or so.. And my machine is just on a random ADSL IP. This thing must have spread REALLY wide!
The patch is availible here
Not any more it's not.. Looks like Microsoft have started responding, probably moved it more prominent..
Wonder when the 'Red Menace' spin from Mr gates sympathisers in the Gvt. will start.
EZ
"Oops, I always forget the purpose of competition is to divide people into winners and losers." - Hobbes
I don't know about strange shellcode, but you made me curious...I browsed the log for my personal webserver (Apache running on LFS) and saw a suspicious request for /default.ida at 16:49 PDT from a site in Taiwan. Searching for that request on the rest of the webserver log (going back maybe a year or so at this point) turned up 21 other requests for the same thing, all earlier today. The requests were coming in from around the world...but the last one was from Taiwan and the two before it were from Red China. These last three requests were within one hour of the beginning of whitehouse.gov's problems. /default.ida sounds like something one might request from an IIS box (instead of /index.html, they usually use /default.htm as the homepage)...would this have been a probe from the punks who pulled this stunt?
(FWIW, other countries that appeared in the log are (in the order they appeared) South Korea, Canada, Japan, and Germany. Several American sites were also on the list (many of them on cable-modem or DSL connections).)
20 January 2017: the End of an Error.
Don't forget we are speaking about Windows machines here, and those are notoriosly bad at managing such "advanced" concepts as timezones. Just whitness the bi-yearly mess that occurs whenever we switch daylight savings time. Windows machines usually run their clock in local time, and have no such concept as location-independant UTC time.
The government cannot take down Microsoft, but Microsoft can take down the government...
*ponder*
Right, so, who wants to build a space station with me and leave this BS behind? I'll bring cookies.
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
scared me at first.. reboot fixes it.. but it comes back..t .asp?url=/technet/security/bulletin/MS01-033.asp) patch.. should clear it up.. I hope, anyway. (-:
upgrade your service packs/critical updates and then run this (http://www.microsoft.com/technet/treeview/defaul
So that's why my DSL router was crapping out every 10 minutes or so this afternoon, after several months of continuous uptime. I knew it couldn't be a configuration problem (there's only so much configuratin' one can do to those things.)
After reading about the trouble Slashdot ran into with their Cisco routers, and the tongue lashing they got for rebooting it without understanding the problem, I'm glad I powercycled it anyway. It did solve the problem, until I got hit again.
While I was rebooting the "turtle," as we call it, my girlfriend, Anne, for some reason got really upset, started crying and moved out. Really odd.
I don't need large brains to have a good time.
lets do a quick grep in the logs ;)
.. ;)
# grep default.ida * | wc -l
5630
woops
Out of curiosity I checked whitehouse.com. If anyone is working the evening shift like me, don't go there from work unless your employer has an very lax internet use policy. In other words it's one of those "Mature Audiences" sites. Just so ya know.
I don't run IIS, but I've been seeing odd things in my logs. It took me a sec to check security focus and learn what it was. Here is an except of a log file so you if see similar you know what's up.
/default.ida?NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN%u9090%u6858% ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u6858%uc bd3%u7801%u9090%u9090%u8190%u00c3%u0003%u8b00%u531 b%u53ff%u0078%u0000%u00=a HTTP/1.0" 400 323 "-" "-"
65.201.146.103 - - [19/Jul/2001:17:58:49 -0400] "GET
The thing on security focus indicating that "default.ida" thing is IIS probes (and/or possibly already compromised systems rescanning is here.
Wheeeee
I don't think this has anything to do directly with the routers. It just happens that the exploit used also affects certain cisco routers (through a well-known bug). It's not attacking the cisco os, the routers just happen to get hit in the crossfire between the infected IIS machines and the target IIS machines.
Jason
===========
This email from the security focus list:
The guys at Eeye have a good overview here.
This is basically just the usual buffer overflow attack that's had a patch available for a month, and by following best practices shouldn't be an issue at all. The really interesting thing is where the guns being gathered are pointed: at whitehouse.gov. Should be an interesting night!
Jason
Dick Cheney: SOMEONE SET UP US THE WORM!
George Bush: MAIN SCREEN TURN ON!
George Bush: IT'S YOU!!
Li Peng: YOU HAVE NO CHANCE. MAKE YOUR TIME.
Li Peng: HAHAHAHAHA
Cisco's vulnerability report (read the date!) says that 2.4.1 is OK.
My ISP is recommending 2.4.2, but I don't know why.
It's all academic to me, because I haven't found a place to download either.
--
314-15-9265
There is common belief that disabling the web interface will prevent this. It's not true; mine's been disabled every since this was first reported a year ago and I still got hit. The problem is that "set web disable" prevents the web server from fiddling the router config, but doesn't actually stop the server from parsing input from port 80, which is what locks up the box.
An improved workaround is to disable the web-admin interface and change its port number with "set web port 53496" (replace with some random port number). At least that'll stop it for the near term.
Long term you need to get updated firmware, but of course Cisco won't distribute firmware directly to customers, even though they have public announcements of the existence of bugs and bugfixes. To actually get the firmware you have to get it from your DSL line provider (Qwest, in my case), and Qwest couldn't care less about security with respect to home users, so they've never bothered to offer fixed versions of CBOS.
--
314-15-9265
We got hit by this, too, although we found it and contained it withing 10 minutes of being infected. The solution is to make sure you've got service pack 2 for Win2K, THEN download the critical updates from Windows update, and reboot. The worm will be gone from memory, and the hole patched. SP2 supposedly contains the patch, but it doesn't work, so you have to install SP2 then the critical update available from Windows Update.
Also, we discovered that all the infected machines had had a file "root.exe" placed in the root dir and the inetpub/scripts directory. Anyone who got hit might want to check for that too.
Of course, the simplest solution is to not run IIS...
Perhaps this is why the patch is not on windows update. Fixed now though.
There have been quite a lot of posts on NANOG about this already, and depletion of memory on Cisco routers causing them to crash.
--
Smegma.
20 lines now, about one coming every 15 mins.
Quite many seem to be coming Taiwanian or other Far-East countries such as Thailand.
GET /default.ida?NNNNNNNNNNNNNNNNNNNNNN ...
There are tons of N's (can you say buffer overflow?) and then stuff after the N's. I've left that out to make it harder for script kiddies.
-ted
I've got 26. Definitely unique IPs as shown by .*$//g" | sort -u | wc -l
grep default.ida apache_access.log | sed "s/
-no broken link
--------------------------------------
... but really, what would have been helpful to many IT readers would have been the link to the Microsoft bulletin and patch download in the /. article.
Ceci n'est pas une sig.
While I don't disagree with your bug report, I want to point out that at 5PM PST, it offically becomes July 20th on GMT. Unless the attack begins on the 21st, I'm still assuming whitehouse.gov will be inaccessable tonight :-)
Doh!
It's not the RIAA or MPAA, but you might like these IPs:
207.46.123.13
207.46.152.122
207.46.153.9
207.46.171.237
207.46.171.61
207.46.171.68
207.46.173.25
207.46.175.96
207.46.186.252
207.46.187.123
207.46.196.55
207.46.196.58
207.46.203.39
207.46.227.38
207.46.230.64
207.46.239.116
207.46.239.117
207.46.239.44
207.46.252.139
207.46.28.158
Each of them has hit default.ida on one server I'm watching. From what I can tell from whois -a, 207.46 is all Microsoft corp! They can't even keep up with their patches.
(btw, on this same server I'm seeing a new unique IP default.ida hit every second)
NT sysadmins who know their shit are on Microsoft's Technical Bulletin list. Because these are hotfixes, they don't go on the public site, because they're 'install only if it fixes a problem you actually have.'
Vintage computer games and RPG books available. Email me if you're interested.
Yeah. It's not at all like that ramen.worm; didn't find many unpatched redhat boxes. Oh, wait.... It's not clueless NT admins, it's clueless admins. Idiocy is platform-agnostic.
Vintage computer games and RPG books available. Email me if you're interested.
Run task manager. Select 'processes.' Open the view menu. Select 'choose columns.' Activate 'thread count.' Then look for a process with 100 threads. At least, from what I've read about the worm. My firewall's been turning these away left, right, and centre.
Vintage computer games and RPG books available. Email me if you're interested.
it attacks 198.137.240.92 not www.whitehouse.gov
that is, it doesn't need to reference the dns server (i was hoping to just add an entry for whitehouse.gov to our dns server since i dont have access to the router side of things)
-f
-f
www.blackant.net
....can't it be the RIAA's and MPAA's webservers?
Sigh. Windows IIS: It's like walking around with a handfull of twenties and giving a loaded gun to any criminal you meet.
Fat-fingered the patch location. Here it is.
SealBeater
-- Its survival of the fittest...and we got the fucking guns!!!
We have been dealing with this all day at my job (colo/hosting). Apprently, it's totally memory resident, so a reboot should clear it. However, its really spreading like wildfire. Also will hang Cisco 675s and 678s, so if you have one of those routers (cable/dsl), disable web access. Also is hanging HP printers with web frontends. The traffic alone is choking some of our smaller routers. The patch is availible here.
SealBeater
-- Its survival of the fittest...and we got the fucking guns!!!
Wow. Same here. Time to do some email.
Half of the webmasters will probably be clueless and accuse me of attacking them.
NOTE: If this is a dynamic IP address and you are an ISP, the above request should be able to help you track down your customer and help them fix this issue.
Now THAT is HILARIOUS. The ISP tracking down the customer and helping them? Heheh.
It's nice of you to make the effort though.
I contacted 3 compromised domains myself... I didn't bother with the dynamic IPs that felt me up.
Of the 22 IPs that felt me up, only 3 were "real" domains. The rest looked like ISP users.
Microsoft Outlook: Making the Goodtimes virus real.
I've been chatting with a friend via Jabber now for an hour or so and he's kind of losing his mind 'cause somebody "cracked" one of the IIS servers where he works. I'm guessing the sysadmin is away and he's looking after the machine right now, going through the logs and stuff trying to figure out what happened. I've been helping him, but I'm inept when it comes to IIS. (I'm an apache-fiend.)
/. and there it is -- a Chinese worm. Damn you, Chinese worms!
So here I wander over to
That'll teach my buddy's sysadmins to watch for those patches. Which is really good advice for everyone, 'cause according to the article, not many people did pay attention to this one.
J
The information about the whitehouse.gov attack was wrong. (Well - its still up :)) In fact the attack is going to start tommorrow, july 20th.
Here is the snippet from bugtraq:
Thanks to Eric from Symantec for tossing us a note about the worm being Date
based and not Time based.
We made an error in our last analysis and said the worm would start
attacking whitehouse.gov based on a certain time. In reality its based on a
date (the 20th UTC) which is tomorrow.
If the worm infects your system between the 1st and the 19th it will attempt
to deface the infected servers web page or try to propogate itself to other
systems. On the 20th all infected threads will attempt to attack
www.whitehouse.gov. This seems to continue until the worm is removed from
the infected system.
Any new infection that happens between the 20th and 28th will most likely be
someone "hand infecting" your system as all other worms should be attacking
whitehouse.gov. If for some reason you are infected between the 20th and the
28th then the worm will begin attacking whitehouse.gov without trying to
infect other systems. This attack will continue indefinitly.
The following are rough numbers, but we felt that it was important to
illustrate the affects this worm can _possibly_ have.
The worm has a timeline like this:
day of the month:
1-19: infect other hosts using the worm
20-27: attack whitehouse.gov forever
28-end of month: eternal sleep
Presumably, this could restart at any point in a new month again.
Also, some stats for the attack:
Each infection has 100 threads
Each thread is going to send about 100k, a byte at a time, which means you
have a (40 for ip + 1 for each byte) which means you have 4.1 megs of data
per thread
100 threads * 4.1megs = 410 Megabytes
This will be repeated again every 4.5 hours or so
Remember, each host can be infected multiple times, meaning that a single
host can send 410MB * # of infections.
We have had reports between 15 thousand and 196 thousand unique hosts
infected with the "Code Red" worm. However, there has been cross infection
and we have heard reports of at least 300+ thousand infections/instances
(machines with multiple infections etc..) of this worm.
If there are 300 thousand infections then that means you have (300,000 * 410
megabytes) that is going to be attempted to be flooded against
whitehouse.gov every 4 and a half hours. If this is true and the worm "works
as advertised" then the fact that whitehouse.gov goes offline is only the
begining of what _can_ possibly happen...
It's been done.
(It's a link to information on RTM's worm, for those who don't feel like clicking the link.)
That doesn't fix the problem with the DSL modems but should avoid the trouble with shutting down the white house. But isn't George heading to Italia soon?
-AD
I'm hit every 5-15 minutes. Hmmmm. Maybe we should not be protecting the innocent. Looks like some attempt at buffer overflow.
65.84.139.36 - - [19/Jul/2001:10:04:54 -0400] "GETHere are the guys that were hitting me. Folks might recognize a few. Have at them!
[root@solo logs]# grep default.ida * | awk '{print $1}' | awk -F: '{print $2}' | sort -u169.207.170.50
193.193.215.41
195.114.67.186
195.200.34.139
196.40.46.250
200.182.20.71
202.113.13.252
203.178.84.2
206.242.192.51
206.251.234.67
207.202.221.176
209.158.17.60
210.85.180.152
211.234.104.145
211.42.161.37
213.236.154.78
216.166.147.30
24.26.222.234
24.41.33.105
63.111.12.10
63.111.224.183
63.208.139.169
64.89.77.186
65.84.139.36
66.22.142.101
66.61.64.188
"Beware of he who would deny you access to information, for in his heart, he dreams himself your master."
I got a little worried there for a sec!
I'm still worried!
Write your congressman. I want to see using a Microsoft server being treated as an act of criminal negligence, like drunk driving.
Haven't we all had enough of this bullspit?
My own webserver had been hit by several thousand of these attempts. When I got Slashdotted for putting up pictures of Bobo, it was bad. But this worm has been saturating my DSL with HTTP GET requests.
Fire and Meat. Yummy.
It's just like HP refusing to write Linux drivers for their scanners. Those Chinese crackers are in bed with Bill Gates! I say let's boycott their products until they start supporting OUR OS!!!
It's not really about monopoly.
I we sure it's a mistake? I hope somebody can get their hands on a reverse DNS lookup of the IPs this RNG generates with the default seed. It may be a purposefully chosen number that attacks its [i]real[/i] target(s) while everyone laments the impending fall of the completely useless whitehouse.gov.
I'm surprised that they don't make the attack list public; while those at the top are probably already up $hit creek sans paddle, those further down may not yet realize just how screwed they truly are. A quick script that runs down the list and sends an e-mail to webmaster@, admin@, whatever@ each ip address effected would probably save millions in lost bandwith and business downtime.
---
(It's a link to information on RTM's worm, for those who don't feel like clicking the link.)
That's the original version; I've got an updated version (lighter bandwidth, typo fixes, etc.) available at http://www.snowplow.org/tom/worm/. I'm going to be quite hard to get in touch with for the next two months, but if you have any questions, feel free to ask and I'll get back to them as soon as I can.
Tom Darby
Obliteracy: Words with explosions
I wonder if its a parody put on by the real W :)
The Lottery:
"Not my manner of thinking but the manner of thinking of others has been the source of my unhappiness." - M
Apache doesn't record the specific HTTP request in the error log, so the grep wouldn't match there.
"Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
I found a couple of these in my access_log:
/default.ida?NNNN ...(many N's)... NNNN%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3%u78 01%u9090%u6858%ucbd3%u7801%u9090%u9090%u8190%u00c3 %u0003%u8b00%u531b%u53ff%u0078%u0000%u00=a HTTP/1.0" 400 324 "-" "-"
:)
x.x.x.x - - [19/Jul/2001:23:45:44 +0200] "GET
There were several from different IPs.
So is this the virus trying to infect my Apache server?
Quote from second CNET article: Marc Maiffret, chief hacking officer of eEye: "If this goes along what it's looking like, parts of the Net will go down." He noted, though, that the code could have an error that causes the worm "to screw up and not work right." no wonder
I can confirm this... I'm a Qwest user with the Cisco675 router/ADSL modem with 2.2 firmware. My connection has dropped 3x today already, requiring a simple power off-on to re-establish the connection.
I haven't been surfing heavily today but there is a noticable slowdown from time to time.
Microsoft doesn't put most security patches on Windows Update. They have a Corporate Windows Update (http://corporate.windowsupdate.microsoft.com), but it's basically just another download site... it doesn't automatically tell you what you need or install it for you.
n /notify.asp), but since they obviously have the Update technology down pat, I don't know why they don't have a version of Windows Update with *all* the hotfixes, not just the "consumer-friendly" ones. It would certainly make setting up new machines easier... instead of downloading and installing twenty files, you should be able to just go to their site and have it do the work for you.
Not that keeping up to date on patches is very difficult (subscribe to their Security Bulletin at http://www.microsoft.com/technet/security/bulleti
They haven't really changed Windows Update since it was introduced with Windows 98 - they've really dropped the ball... Redhat's up2date and Ximian's Red Carpet are both quite a bit better than the current implementation of Windows Update.
--
Convictions are more dangerous enemies of truth than lies.
Convictions are more dangerous enemies of truth than lies.
- Nietzsche
Yeah, but for each one you have to click through 3 times just to get the file. Which means:
a) it's really annoying, and lots of people just won't bother, and...
b) it's really easy to miss one or two
And there's no real way to check (there's a dinky little script available somewhere that'll check for IIS patches, but it's buggy and hard to find).
The Corporate Windows Update site makes them easier to download, but it takes weeks for patches to be put up on it after they've been released, and there's no real way to match them with the associated Bulletins (to know if they need to be re-downloaded, if you've missed any, etc.) And it doesn't allow searching by Service Pack.
In this case, Microsoft's system is just sloppy and unprofessional. There's absolutely no reason for this to be such a pain other than Microsoft isn't putting enough money and attention into its support structure.
Sure, they now allow Patches to be joined together so you only have to reboot once for multiple patches and they allow you to search by Service Pack, but those are baby steps that should've been done years ago... patches today should be instantly updated over the web and shouldn't require reboots in 99% of cases (for all IIS patches, it should just shut down IIS, update the files, and restart). Microsoft's behind the curve, and if I was a corporate system admin, I'd be tempted to switch to Red Hat just because they have a much better update structure.
(For instance, with Red Hat, you type up2date, it launches a graphical wizard which automatically tells you what you need updated, downloads, and installs them. It's like four mouse clicks to completely update your system to latest versions of everything on it.)
--
Convictions are more dangerous enemies of truth than lies.
Convictions are more dangerous enemies of truth than lies.
- Nietzsche
While I was working for the feds,
:-)
I met a worm they called Code Red...
And Code Red hit 100K hosts,
And every host had 3 infections
And every infection had 100 threads
And every thread sent 100k
And every k had a thousand bytes [*]
And every byte was sent in 1 packet
And every packet had a 40-byte header
Headers, packets,
Bytes, k,
Infections, hosts and threads...
Once every month, just to piss off the Feds.
[*] 1024 just doesn't scan well.
I'm a bloodsucking fiend! Look at my outfit!
Fortunately, a trace of the sources indicate that the servers involved are being shut down pretty quickly by their admins.
One alarming aspect is the number of these probes that are obviously coming from servers connected through PPP dial-up accounts.
I wonder how many people have installed IIS on PCs running IIS and don't even know it's running?
News With Attitude
a new Internet worm that takes advantage of a security flaw in Microsoft software
Is this even worth mentioning? I mean, really! Don't all worms take advantage of security flaws in Microsoft software? Why can't someone write a worm to take advantage of Apache for a change? All of these Microsoft servers being compromised are making me jealous. If only I could afford a license of Win2k Server, then I could participate in the excitement as well...
some day....
-Ryan, with the unoriginal sig
I thought that said whitehouse.com! I got a little worried there for a sec!
---
------
Sig