From: Dave Feustel <dfeustel@mindspring.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: Is Xen affected by this x86 hardware security hole?
Date: Tue, 02 May 2006 09:54:35 -0500 [thread overview]
Message-ID: <200605020954.36776.dfeustel@mindspring.com> (raw)
In-Reply-To: <a0a00fa0f096edb9f0ab16d700df633c@cl.cam.ac.uk>
On Tuesday 02 May 2006 08:25, Keir Fraser wrote:
>
> On 2 May 2006, at 14:10, Mark Williamson wrote:
>
> > * X running in dom0 can, in principle, subvert any domain you're
> > running, if X
> > itself gets subverted. A bug in X in dom0 could hang the machine in
> > principle.
>
> Yes, although you are a little better off on Xen -- for example iopl==3
> doesn't let you disable interrupts, as it does on native. However, the
> X server will still have access to most I/O ports and can certainly
> wreak havoc because of that.
>
> For this specific problem, it would make sense to ensure that D_LCK is
> set during boot, so that noone can thereafter modify the SMM memory
> space. You need to know something about PCI space to do that, though,
> so it would make sense for us to leave that to domain0.
>
> -- Keir
Thanks for the resonses.
For those interested in the gory details of a proof-of-concept exploit,
it's all laid out in the 16-page pdf by Loic Duflot:
http://www.ssi.gouv.fr/fr/sciences/fichiers/lti/cansecwest2006-duflot-paper.pdf
--
Lose, v., experience a loss, get rid of, "lose the weight"
Loose, adj., not tight, let go, free, "loose clothing"
next prev parent reply other threads:[~2006-05-02 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 14:02 Is Xen affected by this x86 hardware security hole? Dave Feustel
2006-05-02 13:10 ` Mark Williamson
2006-05-02 13:25 ` Keir Fraser
2006-05-02 14:54 ` Dave Feustel [this message]
2006-05-02 15:46 ` Mark Williamson
2006-05-02 17:18 ` Dave Feustel
2006-05-02 16:08 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2006-05-02 13:54 Ian Pratt
2006-05-02 14:02 ` Mark Williamson
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=200605020954.36776.dfeustel@mindspring.com \
--to=dfeustel@mindspring.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.