All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Damien Miller <djm@mindrot.org>
Cc: "Demi Marie Obenour" <demi@invisiblethingslab.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Xen developer discussion" <xen-devel@lists.xenproject.org>,
	"OpenBSD technical mailing list" <tech@openbsd.org>
Subject: Re: Security support status of xnf(4) and xbf(4)
Date: Mon, 28 Mar 2022 04:12:29 +0200	[thread overview]
Message-ID: <YkEZjYJOcjaRhP89@mail-itl> (raw)
In-Reply-To: <37a4b6-cd56-1993-be2-b5522b9aa4d7@mindrot.org>

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

On Mon, Mar 28, 2022 at 12:45:24PM +1100, Damien Miller wrote:
> On Fri, 25 Mar 2022, Demi Marie Obenour wrote:
> 
> > Linux’s netfront and blkfront drivers recently had a security
> > vulnerability (XSA-396) that allowed a malicious backend to potentially
> > compromise them.  In follow-up audits, I found that OpenBSD’s xnf(4)
> > currently trusts the backend domain.  I reported this privately to Theo
> > de Raadt, who indicated that OpenBSD does not consider this to be a
> > security concern.
> > 
> > This is obviously a valid position for the OpenBSD project to take, but
> > it is surprising to some (such as myself) from the broader Xen
> > ecosystem.  Standard practice in the Xen world is that bugs in frontends
> > that allow a malicious backend to cause mischief *are* considered
> > security bugs unless there is explicit documentation to the contrary.
> > As such, I believe this deserves to be noted in xnf(4) and xbf(4)’s man
> > pages.  If the OpenBSD project agrees, I am willing to write a patch,
> > but I have no experience with mandoc so it might take a few tries.
> 
> Hang on, what is a "malicious backend" in this context? Is it something
> other than the Xen Hypervisor? If not, then it seems not to be a useful
> attack model, as the hypervisor typically has near-complete access to
> guests' memory and CPU state.

No, Xen supports running backends for PV devices in arbitrary domain,
not only dom0. You can read more about it at
https://wiki.xenproject.org/wiki/Driver_Domain
See also Andrew's response, Xen is way more disaggregated than KVM.

Qubes OS makes heavy use of this feature - for example network traffic
never passes through dom0 (which has no network interfaces at all!). You
can read more about it at the link below (especially look for the
diagram at the end, if you want just a quick look):
https://www.qubes-os.org/doc/architecture/

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-03-28  2:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 16:13 Security support status of xnf(4) and xbf(4) Demi Marie Obenour
2022-03-25 22:42 ` Chris Cappuccio
2022-03-25 23:09   ` Demi Marie Obenour
2022-03-25 23:50   ` Andrew Cooper
2022-03-28  1:45 ` Damien Miller
2022-03-28  2:12   ` Marek Marczykowski-Górecki [this message]
2022-03-28  2:13     ` Marek Marczykowski-Górecki
2022-03-28 13:51   ` Demi Marie Obenour
2022-03-28 14:39     ` Mark Kettenis
2022-03-28 20:38       ` Demi Marie Obenour
2022-03-28 23:42         ` Theo de Raadt
2022-03-29  8:16         ` Claudio Jeker
2022-03-29 10:51           ` Roger Pau Monné
2022-03-29 16:22           ` Demi Marie Obenour

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=YkEZjYJOcjaRhP89@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=demi@invisiblethingslab.com \
    --cc=djm@mindrot.org \
    --cc=roger.pau@citrix.com \
    --cc=tech@openbsd.org \
    --cc=xen-devel@lists.xenproject.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 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.