From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL v2 0/2] vnc: fix websocket security issues (cve-2015-1779).
Date: Wed, 1 Apr 2015 17:16:42 +0200 [thread overview]
Message-ID: <1427901405-25602-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
$subject says all, here are the cve-2015-1779 fixes for vnc websockets
from Daniel P. Berrange for 2.3-rc2.
v2 fixes the 32bit build failure.
please pull,
Gerd
The following changes since commit b8a86c4ac4d04c106ba38fbd707041cba334a155:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2015-04-01 11:31:31 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-cve-2015-1779-20150401-2
for you to fetch changes up to 2cdb5e142fb93e875fa53c52864ef5eb8d5d8b41:
CVE-2015-1779: limit size of HTTP headers from websockets clients (2015-04-01 17:12:55 +0200)
----------------------------------------------------------------
vnc: fix websocket security issues (cve-2015-1779).
----------------------------------------------------------------
Daniel P. Berrange (2):
CVE-2015-1779: incrementally decode websocket frames
CVE-2015-1779: limit size of HTTP headers from websockets clients
ui/vnc-ws.c | 115 +++++++++++++++++++++++++++++++++++++++++-------------------
ui/vnc-ws.h | 9 +++--
ui/vnc.h | 2 ++
3 files changed, 88 insertions(+), 38 deletions(-)
next reply other threads:[~2015-04-01 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 15:16 Gerd Hoffmann [this message]
2015-04-01 15:16 ` [Qemu-devel] [PULL v2 1/2] CVE-2015-1779: incrementally decode websocket frames Gerd Hoffmann
2015-04-01 15:16 ` [Qemu-devel] [PULL v2 2/2] CVE-2015-1779: limit size of HTTP headers from websockets clients Gerd Hoffmann
2015-04-01 17:09 ` [Qemu-devel] [PULL v2 0/2] vnc: fix websocket security issues (cve-2015-1779) Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1427901405-25602-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).