full-disclosure - TCP ports 1025-1030 and DCOM exploit

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

From: support at mmicman.com (Edward W. Ray)
Subject: TCP ports 1025-1030 and DCOM exploit

I have found that the RPC service in Windows also uses TCP ports 1025-1030
for communication with domain controllers (DCs).  I found this out by
accident by blocking ports in my Windows 2003 domain and observing failed
RPC connectivity using netdiag command on clients.  I also observed attempts
at connection on TCP port 1025.

Once I added TCP port 1025 to my list of allowed ports and ran netdiag, a
connection on the DC port 1025 and the client (higher port number) was
established.

Is this another possible attack vector?  I have not had time to test it
myself, which is why I am asking.

Regards,

Edward W. Ray
SANS GCIA, GCIH