full-disclosure - RealVNC 4.1.1 Remote Compromise

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: <4468AF8B.7000108@csuohio.edu>
Date: Mon May 15 17:44:31 2006
From: michael.holstein at csuohio.edu (Michael Holstein)
Subject: RealVNC 4.1.1 Remote Compromise

> So what can be done about this exploit?  Does 4.1.2 protect against this
> vulnerability?  And what other mitigation procedures are available for
> this?

Well, VNC hasn't exactly been legendary for security .. but if you do 
run it, one safe(er) way to do so is bind VNC to localhost, and use sshd 
and port-redirection to access it.

Of course, then you've got to pay attention to patches in OpenSSH, but 
that's got a better track record, and allows you to do RSA auth, etc.

Cheers,

Michael Holstein CISSP GCIA
Cleveland State University