From: "Daniel P. Berrangé" <berrange@redhat.com>
To: 江芳杰 <18401698361@126.com>
Cc: qemu-devel@nongnu.org, pjp@fedoraproject.org
Subject: Re: Ask for suggestions for CVE-2019-12928
Date: Mon, 11 Jan 2021 16:22:53 +0000 [thread overview]
Message-ID: <20210111162253.GJ1172772@redhat.com> (raw)
In-Reply-To: <74ca794a.6063.176f21e2fca.Coremail.18401698361@126.com>
On Mon, Jan 11, 2021 at 11:43:53PM +0800, 江芳杰 wrote:
> Hi:
> Sorry to bother you~
> I have read the discussions about CVE--2019-12928 ( https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg01153.html).
> But, for the scenario of PC users, which is no requirement of network access to QMP, there are some mitigating proposes.
> 1. Modify the compilation options to disable QMP.
> 2. Modify command line parsing function to discard the QMP parameters with network configurations.
> 3. PC manager or other manage software make sure only the trusted user can use QMP.
> 4. Other ideas?
No code changes are required at all. The described scenario was simply a
user mis-configuration.
In rare case there can be valid reasons to use QMP on a public IP address,
but anyone doing so must ensure their usage is secure.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next parent reply other threads:[~2021-01-11 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <74ca794a.6063.176f21e2fca.Coremail.18401698361@126.com>
2021-01-11 16:22 ` Daniel P. Berrangé [this message]
2021-01-19 20:17 ` Ask for suggestions for CVE-2019-12928 Dr. David Alan Gilbert
2021-01-20 7:59 ` 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=20210111162253.GJ1172772@redhat.com \
--to=berrange@redhat.com \
--cc=18401698361@126.com \
--cc=pjp@fedoraproject.org \
--cc=qemu-devel@nongnu.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.