full-disclosure - Bad news on RPC DCOM2 vulnerability

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>] [day] [month] [year] [list]

Message-ID: <200310111520.h9BFKO6s023433@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Bad news on RPC DCOM2 vulnerability 

On Sat, 11 Oct 2003 01:28:40 PDT, Peter King <elvi52001@...oo.com>  said:

> why those *security* sites keep *exploits* online even when they know that
this is an unpatched vuln !!!!

(Disclaimer:  I'm explaining the site's logic as I see it.  I may be wrong -
they may just be totally irresponsible and not care at all.  In any case,
I'm
not saying I necessarily agree with it, although I'll admit that it takes a
very large cluestick to get some vendors moving....)

Because the vulnerability is in software from a commercial vendor.  This
actually matters.

An open-source package will often get a patch quickly, because the
"currency"
of the open-source community is to a large degree pride and recognition.
Holes
get patched quickly because it's embarrassing to have a large hole go
unpatched.

A commercial closed-source vendor isn't there for recognition.  It's there
*to
make money*.  Fixing holes *costs* money - as a result, there is a
*dis*incentive to actually fix bugs, unless the number/severity of the bugs
are
*so* bad that it starts affecting sales of the product.

You'll notice that Bill Gates made the "First Great Commitment To Security"
speech only after Microsoft software had gotten burnt by Code Red, Nimda,
and a
large number of Outlook-based malware.

You'll notice that Ballmer made the "Second Great Commitment To Security"
speech last week only after Microsoft software had gotten whacked by Blaster
and Nachi.

You'll notice that even all that malware put together hasn't been enough to
make them admit the basic code base is screwed and needs to be thrown out
and
redone from scratch - because THAT would make a multi-billion dollar hit in
their bottom line.

How fast would Microsoft move, given their choice, if they *didnt* know that
there was an exploit available, and that it was just a matter of time before
the exploit got bolted onto one of the numerous worm sleds already
available?

And *that* my friends, is why they make exploits available.