All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Christian Limpach <Christian.Limpach@xensource.com>
Cc: xen-staging@lists.xensource.com, xen-devel@lists.xensource.com
Subject: Re: RE: [Xen-staging] [xen-unstable] hvm: Remove access to QEMU monitor inVNC server
Date: Tue, 27 Mar 2007 22:18:26 +0100	[thread overview]
Message-ID: <20070327211826.GD3126@redhat.com> (raw)
In-Reply-To: <0326530267625D42A4E36594FDD0D1432EBA8A@exchpamain.ad.xensource.com>

On Tue, Mar 27, 2007 at 02:06:42PM -0700, Christian Limpach wrote:
> > hvm: Remove access to QEMU monitor in VNC server
> > 
> > This fixes a RHEL5 errata and CVE-2007-0998.
> > 
> > The monitor is still accessible in debug builds of ioemu (debug=y).
> > 
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> 
> This change is quite weird since it doesn't disable monitor access when
> using SDL.

Well SDL isn't exposed to the network directly - to access the monitor
via the SDL console, you'd need to first access the X server desktop in
question. Unprivileged local users, or remote user can't typically get 
access to X desktop of the person who started the VM, so its not neccessary
to disable it.

> Also, the additional virtual consoles can be used for giving access to
> things without security implications, like serial ports.

The console enables the users to map the virtual serial port onto a physical
device. Not a huge issue, but still basically a privilege escalation because
it lets users access hardware they'd not otherwise be able to.

> I think a much better fix for the security issue would be to change the
> default monitor output not to be a virtual console.

Yes, long term I expect that if we want to avoid Xen forking still further
from QEMU then we'll need XenD itself to own the monitor channel, because
the monitor is becoming the official way to reconfig stuff on the fly. So
if XenD redirected the monitor to a STDIN/SDOUT then it could safely have
complete control over it & not expose it to the user. This is the approach
we already take in libvirt for managing QEMU & KVM guests & it works quite
well. I didn't do that myself because its much more work & I was prioritizing
the security fix. 

NB, this fix is slightly different from what we actually put in RHEL. The
RHEL version removed the code completely - this version allows it to be
toggled at build time because Keir wanted to keep access for developers
who are doing debugging of HVM guests.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-03-27 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703271524.l2RFOMNg003926@latara.uk.xensource.com>
2007-03-27 21:06 ` [Xen-staging] [xen-unstable] hvm: Remove access to QEMU monitor inVNC server Christian Limpach
2007-03-27 21:18   ` Daniel P. Berrange [this message]
2007-03-27 21:32     ` Christian Limpach
2007-03-27 22:28       ` Daniel P. Berrange
2007-03-27 22:40         ` Christian Limpach
2007-03-27 22:47           ` Daniel P. Berrange
2007-03-27 21:24   ` Anthony Liguori
2007-03-27 21:41     ` Christian Limpach
2007-03-27 21:56       ` Anthony Liguori

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=20070327211826.GD3126@redhat.com \
    --to=berrange@redhat.com \
    --cc=Christian.Limpach@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-staging@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.