From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@gmail.com>, P J P <ppandit@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] doc: document that the monitor console is a privileged control interface
Date: Wed, 3 Jul 2019 09:41:07 -0500 [thread overview]
Message-ID: <8e520489-0cf2-f377-0e14-f8f02a59aae1@redhat.com> (raw)
In-Reply-To: <20190703135411.28436-1-berrange@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 639 bytes --]
On 7/3/19 8:54 AM, Daniel P. Berrangé wrote:
> A supposed exploit of QEMU was recently announced as CVE-2019-12928
> claiming that the monitor console was insecure because the "migrate"
> comand enabled arbitrary command execution for a remote attacker.
command
>
> For this to be a flaw the user launching QEMU must have configured
> the monitor in a way that allows for other userrs to access it. The
users
> exploit report quoted use of the "tcp" character device backend for
> QMP.
> --
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-03 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 13:54 [Qemu-devel] [PATCH] doc: document that the monitor console is a privileged control interface Daniel P. Berrangé
2019-07-03 14:24 ` Philippe Mathieu-Daudé
2019-07-03 14:30 ` Daniel P. Berrangé
2019-07-03 14:41 ` Eric Blake [this message]
2019-07-03 16:37 ` no-reply
2019-07-03 21:56 ` Alex Bennée
2019-07-04 8:50 ` Daniel P. Berrangé
2019-07-04 9:16 ` Alex Bennée
2019-07-04 9:19 ` Daniel P. Berrangé
2019-07-04 9:24 ` Alex Bennée
2019-07-04 1:33 ` no-reply
2019-07-05 7:03 ` Markus Armbruster
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=8e520489-0cf2-f377-0e14-f8f02a59aae1@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).