From: Anthony Liguori <anthony@codemonkey.ws>
To: Roberto Paleari <roberto@security.dico.unimi.it>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU testing methodology & results
Date: Thu, 28 Apr 2011 14:44:42 -0500 [thread overview]
Message-ID: <4DB9C3AA.20907@codemonkey.ws> (raw)
In-Reply-To: <BANLkTim--Mr+j+WX3fPEceAfPC_Xwwaaiw@mail.gmail.com>
On 04/08/2011 02:18 AM, Roberto Paleari wrote:
> Dear QEMU developers,
>
> we are a group of researchers working at the University of Milan,
> Italy. During the last year we focused on automatic techniques to find
> defects inside CPU emulators and virtualizers. Our work has been
> published in different conference papers [1][2][3], and the testing
> methodologies we developed allowed us to find defects in several
> emulators and virtualizers, including QEMU.
>
> In these days we were asked to publicly release our experimental
> results. As these results also include several defects in QEMU, we
> believed it was better to contact you before releasing this material
> to the public.
Just to be clear, at least for x86 CPU emulation, QEMU does not attempt
to achieve perfect fidelity and has some pretty well known "security"
issues. For instance, it does not emulate segment register limits in
any meaningful way.
This does not mean that the guest can break into the host, just that the
guest protection mechanisms aren't always enforced when using TCG.
This is not an issue with KVM though.
Regards,
Anthony Liguori
>
> For this reason, we ask to whom it may concern to contact us privately
> at emufuzzer@security.dico.unimi.it to discuss about the disclosure of
> these results.
>
> Thank you very much for your help,
>
> Footnotes:
> [1] Testing CPU Emulators (http://roberto.greyhats.it/pubs/issta09.pdf)
> [2] Testing system virtual machines
> (http://roberto.greyhats.it/pubs/issta10-kemufuzzer.pdf)
> [3] A fistful of red-pills: How to automatically generate procedures
> to detect CPU emulators (http://roberto.greyhats.it/pubs/woot09.pdf)
>
next prev parent reply other threads:[~2011-04-28 19:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 7:18 [Qemu-devel] QEMU testing methodology & results Roberto Paleari
2011-04-08 19:56 ` Blue Swirl
2011-04-10 19:10 ` Roberto Paleari
2011-04-27 14:46 ` Stefan Hajnoczi
2011-04-27 15:31 ` Roberto Paleari
2011-04-28 19:09 ` Blue Swirl
2011-04-28 19:44 ` Anthony Liguori [this message]
2011-04-29 0:17 ` Peter Maydell
2011-04-29 8:33 ` Paolo Bonzini
2011-04-29 21:35 ` Blue Swirl
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=4DB9C3AA.20907@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=roberto@security.dico.unimi.it \
/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).