full-disclosure - DCOM Exploit MS03-026 attack vectors

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

Message-ID: <3F2AED37.10878.14367D4E@localhost>
From: nick at virus-l.demon.co.uk (Nick FitzGerald)
Subject: DCOM Exploit MS03-026 attack vectors

"Paul Tinsley" <pdt@...khammer.org> wrote:

> Microsoft owns up to the exploit being usable on 135, 139 and 445, I have
> heard rumors of port 80 being vulnerable as well.  ...

Brad Bemis is right -- other ports (and not just port 80) associated 
with IIS _if_  COM Internet Services is enabled are also exploitable.

> ...  I was curious as to
> whether anyone had seen anything using a port other than 135?  ...

Look for messages by Todd Sabin in Bugtraq and/or NTBugtraq and/or 
VulnWatch and/or Full-Disclosure for more details.

> ...  Everything I
> have seen discussed here and elsewhere has been 135 specific.

Well, it is the most widely supported default interface that is 
vulnerable.  It would be a very unusual machine that is vulnerable on 
some other port and _NOT_ on 135, so what is the payoff for writing an 
exploit (at least a "prrof of concept") that tries other ports?

Regards,

Nick FitzGerald