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

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

Message-ID: <tgdi62lnu782a2eb3ote3vqbk9tld72705@4ax.com>
Date: Tue May 16 10:15:07 2006
From: plato at dodgeit.com (plato@...geit.com)
Subject: re: RealVNC 4.1.1 Remote Compromise

Wow, 1 line of code addition to exploit:
	secType=1;

Since I'm sure many have already discovered this (since it is so
trivial), I leave it up to the devious reader to find out where to
insert this.

 BTW: RealVNC 4.1.2 is not affected by this bug.

** Disclaimer: If you find out how to exploit this, do so *only*
against your own systems to see if you are vulnerable. Please do not
exploit others systems since the sysadmins already have a hard enough
time dealing with users and do not need your presents to deal with.