| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Virus-Like Internet Infection Spreading | |
|
||
| Time: 00:25 EST/05:25 GMT | News Source: Washington Post | Posted By: Robert Stein | ||
|
A virus-like infection that was the subject of urgent U.S. government and industry warnings spread rapidly Monday across the Internet, causing computers to mysteriously restart and coordinating an electronic attack against Microsoft Corp. Security experts said the infection, which exploits an unusually dangerous flaw in Windows software, wasn't yet seriously disrupting Internet traffic but posed that risk as it was expected to continue spreading quickly overnight. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 218 Last | Next |
The time now is
11:14:21 PM
ET.
Any comment problems? E-mail us |
| #1 By 2332 (65.221.182.2) at 8/12/2003 3:40:56 AM |
|
Enough is enough. It's clear to me that people simply can't be relied on to click a simple icon and update their computers.
From now on, all Microsoft operating systems should automatically update themselves without any user interaction whatsoever. All the user gets to do is click a button that restarts their computer after the update. And yes, I'm talking about servers and desktops alike. I've often argued that system administrators would hate such an uncontrolled patching system, as any good administrator sets up staging boxes to test all new patches before applying them on product servers or on the network. But it's pretty clear at this point that system administrators ARE STUPID. They don't seem to patch any more regularly than users do. So Microsoft needs to compensate for their stupidity. If a smart admin wants to turn off the feature, the fine. But default, it obviously NEEDS to be on. Otherwise, worms like this will NEVER stop and thing will only get worse. |
| #2 By 143 (199.35.33.212) at 8/12/2003 4:22:27 AM |
|
well said...
|
| #3 By 5912 (62.192.124.170) at 8/12/2003 6:56:33 AM |
| It's stupid that we should have to patch in the first place. This vulnerability is one of the dumbest I have ever hear of. MS should be ashamed of itself for doing such a lousy job in testing its products. |
| #4 By 1868 (24.50.128.109) at 8/12/2003 8:07:54 AM |
|
I got infected and you get a little timer telling you that the system/administrator had a RPC event terminated and it needs to reboot. I was running Norton with all of the latest defs from the 10th, and I have SP1 and just about every other win update save .net framework 1.1 Windows Update didn't and I still don't think it has a fix on it. I found out about it on /. and was lucky to know where to look. But we are all technocrats and we know about tech websites and how to deal with viruses, most users don't. I had 11 calls about the virus yesterday, and at work we've so far had 27 computers get infected too(and they are running XP SP1 and Norton Corporate).
Life goes on....VIRUSES SUCK! |
| #5 By 2332 (65.221.182.2) at 8/12/2003 9:33:12 AM |
|
#5 - That's right, it's stupid that an application with millions of lines of code would have a bug in it. It's very reasonable to expect absolutely no bugs in a piece of software that required engineering comperable to landing on the moon.
There will always be bugs in software. Microsoft tests their code more than just about anybody in the industry. The fact they have bugs is proof that getting rid of all bugs is nearly impossible in any even moderatly complicated software project. I doubt you have the first clue as to what Microsoft does to test their software, and how those testing procedures compare to their competitors. Perhaps you should do a bit of research before you come to your conclusion. #6 - If you had every windows patch, you wouldn't have become infected. The patch for this bug has been available since July 16th. It was on Windows Update within a day of the initial knowledge base article. (Found here: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS03-026.asp) I got my little Windows Update icon no later than the 18th. |
| #6 By 40 (216.68.248.200) at 8/12/2003 9:46:06 AM |
| This one is intresting, there is more to it then everyone is putting forward. I have a Windows 2003 Web server that Saturday started rebooting on it's own, and the only entry was RPC related DLL failures. Dell was blaming my Pix firewall for causing the issue, I was blaming the Nic or software installed, and the unit was patched with all the latest patches. Fixblast from Symantec found no infection, but after re-appling the patch, the System is not rebooting on it's own again. Time to dig deeper into the worm and find out what is going on. |
| #7 By 135 (209.180.28.6) at 8/12/2003 10:19:51 AM |
|
rnmboon - "It's stupid that we should have to patch in the first place. This vulnerability is one of the dumbest I have ever hear of. MS should be ashamed of itself for doing such a lousy job in testing its products. "
Wow, what a very reasonable position. Now could you tell me what operating system I should be running instead? One where there are never any updates or patches because everything is perfect? Thank you! |
| #8 By 1868 (64.24.225.241) at 8/12/2003 2:02:42 PM |
|
Ouch! Burned by not updating windows. Well I guess I'm the one to blame, not Microsoft. I am just weary of there patches, everything before SP1 was great then something happened and I've personally run into more patches problems than I can to describe so I stopped the automatic "sure install a patch" concept. I figured SP1 was good enough once I had gotten it to work. And yes the computers at work were the public ones that weren't behind the firewall.
So inconclusion.... I got burned by SP1 and the evil .Net framework 1.1 and stopped patching and then I got burned again my not patching. Well, let the headaches begin..... |
| #9 By 2332 (216.41.45.78) at 8/12/2003 2:06:57 PM |
|
#11 - I've never been "burned" by a Windows patch, but that's not to say that other people haven't. I'm sure they have.
But I can pretty much guaruntee it's safter to apply all patches then to leave even one unapplied. |
| #10 By 40 (216.68.248.200) at 8/12/2003 2:42:17 PM |
|
Ok, here is what I found, the patch doesn't protect my Windows 2003 web edition completely. I have 2 patched machines, and have been scanned by the Retina Dcom Scanner and show patched, FixBlaster.exe show clean. File dates match on the updates, yet rebooting several times an hour, until I enabled filtering on the Adapter, limiting TCP ports. Server and Enterprise version are not effected. Has anyone else seen this? This post was edited by johnnyq on Tuesday, August 12, 2003 at 14:45. |
| #11 By 5912 (62.192.124.170) at 8/13/2003 6:44:27 AM |
| #5 & #10: this is NOT 'a bug' but more like an open wound. I agree that MS can't test for every bug in the software but this one is of such a stupifying magnitude that you begin to wonder what they are doing up there in Redmond. You can't blame ordinary users for wondering why these things keep on happening again and again while their 'OS of choice' should be the most advanced around! Windows XP should have been the new milestone in personal computing but you can't help thinking that security-wise we have progressed very little since the DOS-days. Trusted computing? Don't make me laugh.. |
| #12 By 2332 (65.221.182.2) at 8/13/2003 9:50:19 AM |
|
#15 - What do you think these bugs look like in code? Have you ever written a line of code in your life?
This bug is likely a single line of code. A single line nestled in among millions of other lines. Frankly, it's amazing any bugs like this are ever discovered. |
| #13 By 5912 (217.121.189.8) at 8/13/2003 1:14:11 PM |
| #16: I'm a professional software developer (VB, C++, ASP, Centura and Notes/Domino), and I can't imagine this 'bug' being just 'one line of code'. Sounds more like they completely forgot to design *any* kind of security-check on the whole DCOM/RPC-mechanism in Windows. |
| #14 By 1845 (12.209.152.69) at 8/13/2003 5:41:31 PM |
|
nm,
With your flair for the dramatic, you don't sound very professional at all. This flaw has existed since Windows 2000. That means it has been around for at least 4 years (since Win2k's RC stages). That means it isn't just Microsoft that missed it. It is also tens of thousands of testers, and hundreds of millions of users of Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Data Center Server, Windows XP Home Edition, Windows XP Professional Edition, Windows Server 2003 Standard, etc. etc. So many users, developers, testers, and this little flaw has evaded everyone for so long. You're such a professional, I'm surprised in all of your wisdom and knowledge you didn't find the flaw yourself. Oh wait, maybe you aren't quite as on top of things as you want us to think you are? |
|
Write Comment
Return to News |
Displaying 1 through 25 of 218 Last | Next |
The time now is
11:14:21 PM
ET.
Any comment problems? E-mail us |
