full-disclosure - The MSBlast Conspiracy Theory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20030815075257.84748.qmail@web20604.mail.yahoo.com>
From: joey2cool at yahoo.com (Joey)
Subject: The MSBlast Conspiracy Theory

> This was such a benign implementation of the serious
> DCOM security risk, that my conspiracy theory
> is ... Microsoft had this worm released on purpose
> in an attempt to get everyone to patch their
> machines before a really threatening version was
> released.

It used dcom.c's bindshell and the transfer method was
TFTP. I don't think Microsoft was behind MSBlast, and
they were probably afraid when it was released. Worms
get more exposure than just security flaws.

> Any of these would cause so much harm to Microsoft
> from the lawsuits and lost business, that they
> couldn't afford to let it remain out there, thus the
> conspiracy theory arises.

Microsoft just got lucky. The possibility of a harder
worm is still out there but it wont effect as many as
it would have before MSBlast. This also is a good
example how home users(obvious) dont patch windows and
how microsoft has yet another vulnerable service, but
this time it wasnt IIS.

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com