OMRF-ISG Archives

OMRF's Information Support Group

omrf-isg@SPEEDY.OUHSC.EDU

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0 (Apple Message framework v552)
Sender:
OMRF's Information Support Group <[log in to unmask]>
Subject:
From:
Todd Walker <[log in to unmask]>
Date:
Sat, 16 Aug 2003 14:16:30 -0500
Content-Transfer-Encoding:
7bit
Content-Type:
text/plain; charset=US-ASCII; format=flowed
Reply-To:
OMRF's Information Support Group <[log in to unmask]>
Parts/Attachments:
text/plain (20 lines)
Food for thought... many have pointed out that the Blaster worm could
have been easily set to do much worse damage than it actually was.
In fact, the author could have simply it to delete the C: drives of all
infected computers, or worse, on August 16th instead of doing a DOS
script against windowsupdate.com only, or it could have had a broader
definition of what to attack at MS as well, shutting down patching
availability
completely.  The article below points out that the worm's release
finally
forced millions of people to patch, stopping the chance of a much worse
worm later exploiting the RPC vulnerability.

Question of the day: could Blaster have been an intentional release by
either the US government, or less likely, MS itself?


Here's the article "The Bright Side of Blaster" from securityfocus

http://www.securityfocus.com/news/6728

ATOM RSS1 RSS2