From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu block-qcow.c block-qcow2.c block-vmdk.c bl...
Date: Tue, 11 Mar 2008 18:30:29 +0100 [thread overview]
Message-ID: <47D6C1B5.2090002@bellard.org> (raw)
In-Reply-To: <E1JZ86x-0004mP-EW@cvs.savannah.gnu.org>
IMHO it would be much simpler to do all the tests in the block format
handlers.
Fabrice.
Aurelien Jarno wrote:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Aurelien Jarno <aurel32> 08/03/11 17:17:59
>
> Modified files:
> . : block-qcow.c block-qcow2.c block-vmdk.c block.c
> block.h block_int.h
>
> Log message:
> Fix CVE-2008-0928 - insufficient block device address range checking
>
> Qemu 0.9.1 and earlier does not perform range checks for block device
> read or write requests, which allows guest host users with root
> privileges to access arbitrary memory and escape the virtual machine.
>
> CVSWeb URLs:
> http://cvs.savannah.gnu.org/viewcvs/qemu/block-qcow.c?cvsroot=qemu&r1=1.15&r2=1.16
> http://cvs.savannah.gnu.org/viewcvs/qemu/block-qcow2.c?cvsroot=qemu&r1=1.10&r2=1.11
> http://cvs.savannah.gnu.org/viewcvs/qemu/block-vmdk.c?cvsroot=qemu&r1=1.19&r2=1.20
> http://cvs.savannah.gnu.org/viewcvs/qemu/block.c?cvsroot=qemu&r1=1.54&r2=1.55
> http://cvs.savannah.gnu.org/viewcvs/qemu/block.h?cvsroot=qemu&r1=1.6&r2=1.7
> http://cvs.savannah.gnu.org/viewcvs/qemu/block_int.h?cvsroot=qemu&r1=1.16&r2=1.17
>
>
>
next prev parent reply other threads:[~2008-03-11 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 17:17 [Qemu-devel] qemu block-qcow.c block-qcow2.c block-vmdk.c bl Aurelien Jarno
2008-03-11 17:30 ` Fabrice Bellard [this message]
2008-03-11 22:23 ` Aurelien Jarno
2008-03-11 22:43 ` Fabrice Bellard
2008-03-11 23:15 ` Aurelien Jarno
-- strict thread matches above, loose matches on Subject: below --
2008-03-11 23:30 Aurelien Jarno
2007-09-16 21:59 Thiemo Seufer
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=47D6C1B5.2090002@bellard.org \
--to=fabrice@bellard.org \
--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).