From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Thomas Huth <thuth@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: Wed, 25 Sep 2019 22:51:21 +0200 [thread overview]
Message-ID: <ca146886-12e5-14c7-7b18-76494b1d7c8f@redhat.com> (raw)
In-Reply-To: <20190925130331.27825-1-thuth@redhat.com>
Hi Thomas,
On 9/25/19 3:03 PM, Thomas Huth wrote:
> Both, "rom->addr" and "addr" are derived from the binary image
> that can be loaded with the "-kernel" paramer. The code in
> rom_copy() then calculates:
>
> d = dest + (rom->addr - addr);
>
> and uses "d" as destination in a memcpy() some lines later. Now with
> bad kernel images, it is possible that rom->addr is smaller than addr,
> thus "rom->addr - addr" gets negative and the memcpy() then tries to
> copy contents from the image to a bad memory location. In the best case,
> this just crashes QEMU, in the worst case, this could maybe be used to
> inject code from the kernel image into the QEMU binary, so we better fix
> it with an additional sanity check here.
>
> Cc: qemu-stable@nongnu.org
> Reported-by: Guangming Liu
> Buglink: https://bugs.launchpad.net/qemu/+bug/1844635
"This page does not exist, or you may not have permission to see it."
This seems security related. Shouldn't we open a CVE for this?
https://wiki.qemu.org/SecurityProcess#CVE_allocation
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.
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> hw/core/loader.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/core/loader.c b/hw/core/loader.c
> index 0d60219364..5099f27dc8 100644
> --- a/hw/core/loader.c
> +++ b/hw/core/loader.c
> @@ -1281,7 +1281,7 @@ int rom_copy(uint8_t *dest, hwaddr addr, size_t size)
$ git show 235f86ef014
Date: Thu Nov 12 21:53:11 2009 +0100
This function is old and poorly documented.
> if (rom->addr + rom->romsize < addr) {
> continue;
> }
> - if (rom->addr > end) {
> + if (rom->addr > end || rom->addr < addr) {
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> break;
> }
>
>
next prev parent reply other threads:[~2019-09-25 20:53 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é [this message]
2019-09-26 5:53 ` Thomas Huth
2019-09-26 5:58 ` Thomas Huth
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=ca146886-12e5-14c7-7b18-76494b1d7c8f@redhat.com \
--to=philmd@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=thuth@redhat.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).