From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
mdroth@linux.vnet.ibm.com, qemu-stable@nongnu.org
Subject: Re: [PATCH] hw/core/loader: Fix possible crash in rom_copy()
Date: Thu, 26 Sep 2019 07:58:26 +0200 [thread overview]
Message-ID: <fc1616b5-1404-166a-6cae-c729ce77b1b3@redhat.com> (raw)
In-Reply-To: <ca146886-12e5-14c7-7b18-76494b1d7c8f@redhat.com>
On 25/09/2019 22.51, Philippe Mathieu-Daudé wrote:
[...]
> Let's say I have write access to a LAN TFTP server used by some PXE
> bootloader where I can store my crafted nasty kernel, then I get this score:
>
> https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C&version=3.1
>
> CVSS Base Score: 9.6
> CVSS Temporal Score: 8.6
>
> Which seems quite high.
I don't think you can trigger this bug this way. If you load your kernel
via a PXE server, the ELF parsing will be done by the bootloader, won't
it? I think you can only trigger this bug here if you load your kernel
via the "-kernel" command line parameter of QEMU (or the generic-loader
device), so it's not a real guest escape, as far as I can see.
Thomas
next prev parent reply other threads:[~2019-09-26 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 13:03 [PATCH] hw/core/loader: Fix possible crash in rom_copy() Thomas Huth
2019-09-25 13:22 ` Michael S. Tsirkin
2019-09-25 13:51 ` Paolo Bonzini
2019-09-25 20:51 ` Philippe Mathieu-Daudé
2019-09-26 5:53 ` Thomas Huth
2019-09-26 5:58 ` Thomas Huth [this message]
2019-09-26 6:11 ` Philippe Mathieu-Daudé
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=fc1616b5-1404-166a-6cae-c729ce77b1b3@redhat.com \
--to=thuth@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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).