See bug #136916 for further details.
KDE team, please advise/patch.
Is there a patch for this? because I was waiting for that when the bug was open, and seems nothing was posted while I was away ...
We haven't identified whether the bundled version is affected, I think. I'm not even sure upstream knows about the libvncserver problem (same for vino). Jaervosz, maybe we should pull in Tavis? Diego, I take it you didn't hear anything about this upstream?
At least, there are no open bugs about this upstream. Thus, no patches either.
Nothing on the sekrit mailing list (kde-packager) where I was expecting the security patch. That's why I was waiting from someone to post the patch to libvncserver to see if it applied..
I'm not sure which version is bundled with KDE, but bug #136916 has a patch.
(In reply to comment #7) > I'm not sure which version is bundled with KDE, but bug #136916 has a patch. Sorry, but I fail to see any patch there. In bug #136916#c22 the patch is requested, however no one replied. Please, could you point us to the exact location of the patch? Or is it under net-libs/libvncserver/files?
KDE security team contacted. @commment #8: See URI for upstream libvncserver patch.
The patch does not apply, because auth.c is waaaay different. The libvncserver version used seems to be somewhere between 0.3 and 0.4
I dug around a bit in the sources, and my opinion is that krfb's bundled code is a _very_ old version, so old in fact that it probably isn't vulnerable. From what I see it only supports protocols up to 3.3, and there seems to be no handshake for various authentication types between server and client, which IIRC is the problem (authNONE is accepted even when it was not advertised) because that was introduced in later versions of the protocol (3.7 or such). My personal conclusion is that this old version is not vulnerable to the specific bug we're dealing with here, but I'd rather have someone familiar with VNC or from the Auditing team confirm this (read as: "do not rely on what I say" .-)
Upstream confirms that the version is so old that it is not vulnerable. Thx everyone.