Code Red Worm Spreading, Set To Flood Whitehouse 306
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."
Re:what it looks like (Score:3)
Fake worm warning makes ALL OF US flood website! (Score:5)
Re:what it looks like (Score:2)
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
---
Re:If you don't run IIS but.... (Score:2)
Pretty good simulation/dry run... (Score:2)
Be interesting to hear the analyses about this one when it's all over.
Re:So, who's REALLY in charge... (Score:2)
We should take a lot of weed with us.
high5!~ (Score:2)
Re:So, who's REALLY in charge... (Score:2)
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.
Re:Cisco DSL routers (Score:3)
None of my int's are good enough.
Re:Cisco DSL routers (Score:3)
http://www.qwest.com/dsl/customerservice/csco675up s.html [qwest.com]
p s.html [qwest.com]
http://www.qwest.com/dsl/customerservice/csco678u
Re:So, who's REALLY in charge... (Score:2)
*cough
Re:Why or why.... (Score:2)
Jeez, if this is coming to my obscure neck of the woods... gonna be a hell of a night for W's IT staff...
Re:Probes coming from dial-up connections too! (Score:3)
Wonder if that's vulnerable.
What about an automatic antidote? (Score:2)
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).
Re:hmm (Score:2)
-Moose
Re:hmm -- UPDATE (Score:3)
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
Re:Fake worm warning makes ALL OF US flood website (Score:2)
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?
Re:Fake worm warning makes ALL OF US flood website (Score:2)
Be sure to check out the inaugural address link.
Re:Fake worm warning makes ALL OF US flood website (Score:2)
'Course I'm not browsing whitehouse.gov at -1.
Re:Why or why.... (Score:2)
Or maybe you were just unlucky
Re:Cisco DSL routers (Score:2)
---
ha! (Score:2)
---
Re:what it looks like (Score:2)
On 2000 and on system where some non-stupid admin did the initial installation (but not maintenance
Ciao,
Rob!
Re:Windows Update (Score:2)
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!
--
And while we're confirming stuff (Score:2)
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.
Re:hmm -- UPDATE (Score:2)
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...
Re:Update! (Score:2)
--
Re:Update! (Score:2)
--
Re:So, who's REALLY in charge... (Score:3)
Tempting, but I block cookies whenever I can. If you bring some beer and steak, I'm there.
time h@X0R (Score:2)
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?
Re:Proactivity (Score:2)
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).
--------------
Press DOS attack (Score:5)
Re:Update! (Score:2)
100,000 (Score:3)
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 [whitehouse.gov] INFORMATION BEFORE IT'S TOO LATE!!!
Re:Dealing with this all day (Score:2)
Re:Why M$ ? (Score:2)
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 [grc.com].
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
Re:Update! (Score:2)
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)
Re:Another update- random IPs (Score:2)
It does show up how many people cannot be bothered to set up reverse DNS though. THe only likely problem is wastage of bandwidth.
Re:what it looks like (Score:2)
Re:Dealing with this all day (Score:2)
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
Re:hmm (Score:2)
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).)
Re:Update! (Score:2)
So, who's REALLY in charge... (Score:5)
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.
I've had to deal with this all day.. (Score:4)
upgrade your service packs/critical updates and then run this (http://www.microsoft.com/technet/treeview/defaul
Ah HA! (Score:4)
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.
Re:Let's see... /var/log/apache (Score:2)
# grep default.ida * | wc -l
5630
woops
Re:WhiteHouse.gov? Thank God! (Score:2)
If you don't run IIS but.... (Score:5)
65.201.146.103 - - [19/Jul/2001:17:58:49 -0400] "GET
The thing on security focus [securityfocus.com] indicating that "default.ida" thing is IIS probes (and/or possibly already compromised systems rescanning is here [securityfocus.com].
umm... are you sure? (Score:2)
Jason
Another update- random IPs (Score:2)
===========
problems with the patch (Score:2)
This email from the security focus list:
Good description here: (Score:3)
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
Obligatory reference: (Score:5)
George Bush: MAIN SCREEN TURN ON!
George Bush: IT'S YOU!!
Li Peng: YOU HAVE NO CHANCE. MAKE YOUR TIME.
Li Peng: HAHAHAHAHA
Re:Cisco DSL routers (Score:2)
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.
--
Cisco DSL routers (Score:5)
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.
--
Re:Another update- random IPs (Score:2)
<P>
GET
<P>
this came from about 3 dozen different IP's today. a few were from corporate servers... so I notified the webmasters... but the index page of these servers were not replaced... so I have no idea what the exception was.
<P>
more info can be found on deja or <a href="http://www.securityfocus.com/templates/arch
Re:Dealing with this all day (Score:2)
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...
This is why! (Score:3)
Re:So, who's REALLY in charge... (Score:2)
Yes -- for example, if I shoot someone, that's illegal. If the government subsequently locks me up for 20 years (which is a form of physical force), that's perfectly legal.
I thought the raison d'etre of the 2nd Amendment was to prevent the government gaining a monopoly of force.
Right -- it's more complicated than that. As a citizen, you have the right to defend yourself -- and if necessary, to respond to an act of force with violence; but only the government can legally initiate the use of force. (That's Ayn Rand's view anyway...)
Infrastructure Issues (Score:3)
There have been quite a lot of posts on NANOG [merit.edu] about this already, and depletion of memory on Cisco routers causing them to crash.
--
Let's see... /var/log/apache (Score:2)
20 lines now, about one coming every 15 mins.
Quite many seem to be coming Taiwanian or other Far-East countries such as Thailand.
what it looks like (Score:5)
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
Re:Why or why.... (Score:2)
I've got 26. Definitely unique IPs as shown by .*$//g" | sort -u | wc -l
grep default.ida apache_access.log | sed "s/
Re:Should have open sourced it... (Score:2)
--------------------------------------
bashing M$ IS fun... (Score:5)
Re:Update! (Score:5)
Re:Why or why.... (Score:5)
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)
Re:This is why! (Score:2)
pétard
Re:Windows Update (Score:2)
Re:Windows Update (Score:2)
Re:Detection (Score:3)
Re:Another update- random IPs (Score:2)
I hope you see this
We watched a worm today hitting our IIS machine. With a few hacked up perl scripts I wrote I captured some of the HTTP requests.
Has anyone seen something like.. (from memory bear with me)
Something like that.. I knowt he middle was 9090. I dont think this was the china worm.. our index page wasnt replaced or hacked. It continually shut down our IIS service. Removing our IIS mappings to everything but the extensions we needed stopped the crash. It became progressively worse to the point where our ISDN being hit with these requests every second.
I found the security bulletin (033?) on the MS site etc. Its pretty interesting. Anyhow.. Just figured id share.
Jeremy
Re:Update! (Score:4)
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
Re:So, who's REALLY in charge... (Score:2)
But honestly, we have to be economical- how about a few drums of hash oil? I mean, we only have so much space!
Re:So, who's REALLY in charge... (Score:2)
Re:So, who's REALLY in charge... (Score:2)
In any case, you can leave whenever you want, no one is keeping you here. I like it, though, so I guess I'll just swim in my own sea of hash oil down on Earth. However, I can sell you some sweet plans on making a rocketship...
Why or why.... (Score:5)
Sigh. Windows IIS: It's like walking around with a handfull of twenties and giving a loaded gun to any criminal you meet.
Re:Another update- random IPs (Score:2)
---
Re:So, who's REALLY in charge... (Score:2)
---
Re:Another update- random IPs (Score:2)
Good point about the reverse DNS lookups, actually most of the ones I checked didn't even have a valid domaine name. Probably they are just Windows 2000 users with cable modems who leave their computers on all day, and don't even realize they are infected.
---
Re:Dealing with this all day (Score:2)
SealBeater
Dealing with this all day (Score:4)
SealBeater
Re:Why or why.... (Score:3)
22 hits to me, though my overworked cable modem serves about 1000 unique visitors a day.
Then again traffic shouldn't matter... according to the articles the IP addresses to attack are produced by a pseudo-random algorithm... so those of us with a handful of hits have IPs that are way down on the algorithm's list.
My first hit was at 9:20 AM, the last was at 4:04 PM.
Can Microsoft Protect You From Itself? (Score:3)
Microsoft Outlook: Making the Goodtimes virus real.
Update! (Score:4)
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...
Re:Good description here: (Score:5)
Re:what it looks like (Score:3)
If the DDoS doesn't bother spoofing the source address (and I didn't see anything to indicate that it did) and if it doesn't bother closing the hole, I find it interesting that the target of the attack could hypothetically "hack back".
(20 hits for default.ida in the logs at one job, 26 at the other. I (heart) Apache.)
Re:Affects IIS? (Score:3)
It's been done [software.com.pl].
(It's a link to information on RTM's worm, for those who don't feel like clicking the link.)
Re:what it looks like (Score:3)
Oh nos! You've called me a dumbass. My penis will now shrink, and I'll forever be a hollow shell of a man.
And assuming I'm understanding you correctly, by zombies you're referring to just an arbitrary exploited machine, running the DDoS on behalf of a third party. I was aware of this fact when I posted my comment. I certainly was under no misapprehension that a given DDoS machine was being run by the person who created the worm.
But that doesn't change the fact that, under the conditions I stated, the person on the receiving end of the attack could hypothetically reexploit each machine to (if they're nice) disable the worm or (if they're mean) wipe the system altogether. Besides, the owners of the machines in question share some culpability in their failure to properly administer and secure their systems.
Write Your Congressman NOW! (Score:3)
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 [glowingplate.com], it was bad. But this worm has been saturating my DSL with HTTP GET requests.
Re:Write Your Congressman NOW! (Score:4)
It's just because Microsoft is the number one webserver that the worm is targetted towards it. If Linux were the number one webserver the worm would target it.
Hmmm... Uhhh. Microsoft primarily makes operating systems which repeatly prove themselves marginal for desktop use, and criminally inadequate for anything requiring stability or security.
I think you're attempting to imply that IIS server, which comes free - though hobbled to various degrees - with all versions of NT and 2000, is the number one webserver.
That's mighty good crack that you're smoking [netcraft.com].
P.S. Drunk driving is not as bad an activity as you describe.I love drunk driving. It's a lot of fun. A friend of mine used to work in an automotive wrecking yard, and we used to love cracking open a few beers and driving around the yard in one of the junkers that came in under its own power. It was a great way of spending a Friday evening when I was in high school. I assure you, 50-foot-tall mountains of crushed cars are a lot harder to avoid after 6 beers. Even worse, 50-foot-tall mountains of crushed cars are a lot harder than uncrushed cars. They don't collapse well in accidents after they've been through the Al-jon. One might even suggest that they have less crush space. Especially the silly little Hondas.
You know what? I love my cars, and I love my beer. But the two don't mix. I don't drive (on public roads, anyway) if I've had even one beer.
Old people kill more people just because of senility, than drunk drivers.Uh-huh. Yeah. You fascinate me.
Re:Cisco DSL routers (Score:4)
http://www.qwest.com/dsl/customerservice/win675ups .html [qwest.com]
Re:Windows Update (Score:3)
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.
Re:Windows Update (Score:3)
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.
Apologies to St. Ives.... (Score:5)
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.
Probes coming from dial-up connections too! (Score:3)
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 [7amnews.com]
Should have open sourced it... (Score:5)
Re:So, who's REALLY in charge... (Score:4)
Affects IIS? (Score:4)
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....
WhiteHouse.gov? Thank God! (Score:4)
---