From: Chris Cappuccio <chris@nmedia.net>
To: Demi Marie Obenour <demi@invisiblethingslab.com>
Cc: Roger Pau Monn? <roger.pau@citrix.com>,
Marek Marczykowski-G?recki <marmarek@invisiblethingslab.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: Fri, 25 Mar 2022 15:42:36 -0700 [thread overview]
Message-ID: <Yj5FXBj7qKIvs94O@ref.nmedia.net> (raw)
In-Reply-To: <Yj3qW/y20htoSvuK@itl-email>
Demi Marie Obenour [demi@invisiblethingslab.com] 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.
>
A malicious backend could completely compromise the virtual host in an
infinite number of ways. Perhaps a small patch to find incorrect values
would be of value, but even then, a patch would only be a very slight
improvment. If you patch the manual page, should OpenBSD start putting
notifications in all manual pages that a compromised virtual machine
backend may compromise the integrity of the virtual host?
Chris
next prev parent reply other threads:[~2022-03-25 23:36 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 [this message]
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
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=Yj5FXBj7qKIvs94O@ref.nmedia.net \
--to=chris@nmedia.net \
--cc=demi@invisiblethingslab.com \
--cc=marmarek@invisiblethingslab.com \
--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.