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]

Message-ID: <20030728001544.58614.qmail@web80606.mail.yahoo.com>
From: seclistaddress at yahoo.com (manohar singh)
Subject: DCOM RPC exploit (dcom.c) 

Well,

So far about a 100 emails on this subject (dcom.c),
and  all this is doing is irritate everybody.

Guys, this IS an unmoderated list, and people WILL
post exploits. Clear and simple. Let's just grow up,
and get back to work instead of cribbing in public
forums.

ms

--- Valdis.Kletnieks@...edu wrote:
> On Sat, 26 Jul 2003 22:29:56 CDT, Ron DuFresne said:
> > I'm just trying to understand how corporate
> networks would/should be at
> > risk with this, why port 135 would not be filtered
> already limiting
> > exposure.  Is there a reason why it would not be
> that I'm missing?  The
> 
> It's the rare corporate net indeed that doesn't have
> a single remotely
> exploitable copy of IE or Outlook left in its entire
> address space.
> 
> And Slammer proved quite well that having a firewall
> doesn't stop squat.
> 

> ATTACHMENT part 2 application/pgp-signature 

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com