From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35841) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YcsJ0-0007uA-G1 for qemu-devel@nongnu.org; Tue, 31 Mar 2015 05:17:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YcsIx-0001S9-7r for qemu-devel@nongnu.org; Tue, 31 Mar 2015 05:17:54 -0400 Received: from mail-ig0-f173.google.com ([209.85.213.173]:33305) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YcsIx-0001S4-30 for qemu-devel@nongnu.org; Tue, 31 Mar 2015 05:17:51 -0400 Received: by ignm3 with SMTP id m3so8848045ign.0 for ; Tue, 31 Mar 2015 02:17:50 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1427212260.18768.28.camel@nilsson.home.kraxel.org> References: <1427151502-14386-1-git-send-email-berrange@redhat.com> <1427212260.18768.28.camel@nilsson.home.kraxel.org> From: Peter Maydell Date: Tue, 31 Mar 2015 10:17:29 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH 0/2] CVE-2015-1779: fix denial of service in VNC websockets List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: QEMU Developers On 24 March 2015 at 15:51, Gerd Hoffmann wrote: > On Mo, 2015-03-23 at 22:58 +0000, Daniel P. Berrange wrote: >> The VNC websockets protocol decoder has two places where it did >> not correctly limit its resource usage when processing data from >> the client. This can be abused by a malicious client to cause QEMU >> to consume all system memory, unless it is otherwise limited by >> ulimits and/or cgroups. These problems can be triggered in the >> websockets layer before the VNC protocol actually starts, so no >> client authentication will have taken place at this point. > > Hmm, with patch 1/2 applied novnc disconnects frequently. Boot messages > on the text (framebuffer) console seems to work fine. But after logging > in via gdm and trying to do stuff in gnome shell problems are starting. Any further progress here? Ideally I'd like to get a fix for this CVE into rc2... thanks -- PMM