full-disclosure - Cox is blocking port 135

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: joey2cool at yahoo.com (Joey)
Subject: Cox is blocking port 135 - off topic

I don't think DCOM is used on any other port besides
135. When i disabled dcom using dcomcnfg.exe, the only
port that stopped listening was 135.

and for the specifics for how the buffer overflow
works(http://www.lsd-pl.net/special.html) -
"In a result of implementation error in a function
responsible for instantiation of DCOM objects, remote
attackers can obtain remote access to vulnerable
systems."

People claim that the same buffer overflow works on
the SMB port(445) which is an entirely different
service, but can they prove it?

--- Anthony Clark <volkam@...cast.net> wrote:
> Right..
> 
> /* Windows 2003 <= remote RPC DCOM exploit
>  * Coded by .:[oc192.us]:. Security
>  * Modified by rogers@...et
>  *
>  * Features:
>  *
>  * -d destination host to attack.
>  *
>  * -p for port selection as exploit works on ports
> other than
> 135(139,445,539 etc)

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