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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3F377D8B.27395.454A4381@localhost>
From: nick at virus-l.demon.co.uk (Nick FitzGerald)
Subject: Cox is blocking port 135 - off topic

joey2cool@...oo.com wrote:

> cox does block port 445 also, but i havent seen any
> exploits that use that port. even though its said that
> port 445 is vulnerable, where is the POC?

Well, regardless of whether there are any DCOM RPC exploits or worms 
based thereon using 445 or not, there certainly are many other worms 
and scripted distribution mechanisms used for RATs, IRC bot net agents, 
etc that either deliberatly only target, or incidentally use port 445. 
As the level of activity of these things has been high for some time 
and that port is typically exposed by default in the most vulnerable 
groups of users, ISPs catering to those market segments would do well 
to consider blocking those ports, at least on their dial-up and other 
"consumer" offerings.

Regards,

Nick FitzGerald