Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | [UNIX] RealVNC Authentication Bypass |
|---|---|
| Date: | 15 May 2006 17:08:06 +0200 |
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com - - promotion The SecuriTeam alerts list - Free, Accurate, Independent. Get your security news from a reliable source. http://www.securiteam.com/mailinglist.html - - - - - - - - - RealVNC Authentication Bypass ------------------------------------------------------------------------ SUMMARY "VNC (Virtual Network Computing) software makes it possible to view and fully-interact with one computer from any other computer or mobile device anywhere on the Internet." Improper security measures allow attackers to bypass RealVNC authentication. DETAILS Vulnerable Systems: * RealVNC version 4.1.1 As documented in rfbproto.pdf by Tristan Richardson, the RFB (remote frame buffer) protocol performs an initial handshake which allows clients and servers to negotiate appropriate authentication measures. There are several methods of authentication, including the standard DES Challenge-Response, as well as an option to disable authentication completely. Due to an incorrect implementation, clients are able to force the server to disable authentication, and allow login without a password. Proof of Concept: 1. Server sends its version, "RFB 003.008\n" 2. Client replies with its version, "RFB 003.008\n" 3. Server sends 1 byte which is equal to the number of security types offered 3a. Server sends an array of bytes which indicate security types offered 4. Client replies with 1 byte, chosen from the array in 3a, to select the security type 5. The handshake, if requested, is performed, followed by "0000" from the server In RealVNC 4.1.1 and possibly prior versions which implement RFB 003.008 (though not RealVNC 4.0), the server does NOT perform a check to determine if the byte sent by the client in step 4 has actually been offered by the server in step 3a. In effect, authentication is moved from the server side to the client side. It is possible to force your client to simply request "Type 1 - None" as the security type, and gain access to the server without having to go through the time consuming and cumbersome password entry field. Here is a typical packet dump: Server -> Client: 52 46 42 20 30 30 33 2e 30 30 38 0a <- Server version Client -> Server: 52 46 42 20 30 30 33 2e 30 30 38 0a <- Client version Server -> Client: 01 02 <- One field follows... and that field is 02 (DES Challenge) Client -> Server: 01 <- Ahh, the lovely 1 byte exploit! Beautiful, isn't it? Server -> Client: 00 00 00 00 <-- Authenticated! Workaround: Run VNC servers behind firewall, and use SSH tunnels for communication. ADDITIONAL INFORMATION The information has been provided by <mailto:iamjamesevans@gmail.com> James Evans. ======================================== This bulletin is sent to members of the SecuriTeam mailing list. To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@securiteam.com In order to subscribe to the mailing list, simply forward this email to: list-subscribe@securiteam.com ==================== ==================== DISCLAIMER: The information in this bulletin is provided "AS IS" without warranty of any kind. In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [NEWS] Apple QuickTime FPX Integer Overflow, SecuriTeam |
|---|---|
| Next by Date: | [EXPL] RadLance Directory Traversal (Exploit), SecuriTeam |
| Previous by Thread: | [NEWS] Apple QuickTime FPX Integer Overflow, SecuriTeam |
| Next by Thread: | [EXPL] RadLance Directory Traversal (Exploit), SecuriTeam |
| Indexes: | [Date] [Thread] [Top] [All Lists] |