full-disclosure - DCOM RPC exploit (dcom.c)

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]

From: chows at ozemail.com.au (gregh)
Subject: DCOM RPC exploit  (dcom.c)

----- Original Message ----- 
From: Chris Paget 
To: Len Rose 
Cc: full-disclosure@...ts.netsys.com 
Sent: Sunday, July 27, 2003 12:08 PM
Subject: Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)

Len,

IMHO there's a difference between "security through obscurity" and posting
working exploit code.  Knowing that there is a vulnerability in DCOM, accessible
over a range of RPC mechanisms (primarily 135/tcp) is all that most
administrators need to know.  It's one thing knowing that you can kill a person
with a gun, and it's another to give away firearms.

Just my $0.02:

Shoot the messenger - that always stops the bad event happening.

Sorry for the sarcasm. I can never see the point in "If we don't tell the enemy how to build a nuclear weapon they never will so we are safer as a result" logic.

Greg - you may call me a "Jihad O'Clue." if you wish.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20030727/327565db/attachment.html