full-disclosure - Terminal Server vulnerabilities

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

Message-ID: <190DFDD2F99A65469B4B15D3658C0D2BC5A495@ptc6.ponderosatel.com>
From: daniels at Ponderosatel.com (Daniel Sichel)
Subject: Terminal Server vulnerabilities

I am currently locked in a death struggle with Microsoft's server
product group. They have dropped support for the IAS (RADIUS) mmc in
server 2003 and the 2000 version won't work under XP SP2. Their solution
is to user terminal server to control the server remotely to manage
RADIUS. Naturally  I don't like this answer because of horror stories I
have heard about Terminal server. They claim there are no unfixed
vulnerabilities to Terminal Server on Windows Server 2000 Service Pack
4. 

I find that hard to believe and I know you guys will know if they are
full of it, or they are correct. Please let me know ASAP of any CURRENT
vulnerabilities int Terminal Server.

Dan Sichel
Network Engineer
Ponderosa Telephone
daniels@...derosatel.com (559) 868-6367

P.S. the MMC is worse, it requires that port 139 or 445 be opened, but
that is not the point, I suspect they are feeding me a line and I want
to prove it. Thanks.