full-disclosure - [lists] 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2802c522050126085067b32e33@mail.gmail.com>
From: jrickman at gmail.com (Jonathan Rickman)
Subject: [lists] Terminal Server vulnerabilities

On Tue, 25 Jan 2005 14:38:30 -0600, Curt Purdy <purdy@...man.com> wrote:

> The problem with terminal server is not any vulnerablities that can be
> exploited, but the fact that administrator can be bruteforced (6 attempts
> followed by reconnect) and that it is screaming its existence on port 3889.
> If you use it, definitely change the port in the registry.

You can use the local security policy to prevent administrators from
logging in via terminal services and then enable "run as" for
administrative tasks...which should be done anyway. Changing the port
number is another good step though.

--
Jonathan