Full Disclosure mailing list archives
Re: RealVNC 4.1.1 Remote Compromise
From: Joachim Schipper <j.schipper () math uu nl>
Date: Mon, 15 May 2006 18:36:56 +0200
On Mon, May 15, 2006 at 07:58:10AM -0500, Dixon, Wayne wrote:
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?
The best solution is not to run a VNC service using no more than it's
own authentication. Most offer only password auth, which is quite simply
insufficient. Use some auth scheme based on certificates or somesuch -
ssh, IPSec and OpenVPN all offer this capability.
Joachim
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- RealVNC 4.1.1 Remote Compromise James Evans (May 15)
- RE: RealVNC 4.1.1 Remote Compromise Dixon, Wayne (May 15)
- Re: RealVNC 4.1.1 Remote Compromise Joachim Schipper (May 15)
- Re: RealVNC 4.1.1 Remote Compromise Michael Holstein (May 15)
- Re: RealVNC 4.1.1 Remote Compromise Dave "No, not that one" Korn (May 16)
- <Possible follow-ups>
- Re: RealVNC 4.1.1 Remote Compromise Juha-Matti Laurio (May 15)
- re: RealVNC 4.1.1 Remote Compromise plato (May 16)
- Re: RealVNC 4.1.1 Remote Compromise ad () heapoverflow com (May 16)
- RE: RealVNC 4.1.1 Remote Compromise Krpata, Tyler (May 19)
- Re: RealVNC 4.1.1 Remote Compromise ad () heapoverflow com (May 19)
- Re: RealVNC 4.1.1 Remote Compromise Matt Venzke (May 19)
- Re: RealVNC 4.1.1 Remote Compromise ad () heapoverflow com (May 19)
- RE: RealVNC 4.1.1 Remote Compromise Dixon, Wayne (May 15)
