From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=48725 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q2Qd5-0004RX-TM for qemu-devel@nongnu.org; Wed, 23 Mar 2011 12:09:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q2Qd4-00065s-Vi for qemu-devel@nongnu.org; Wed, 23 Mar 2011 12:09:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:63741) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q2Qd4-00065j-HH for qemu-devel@nongnu.org; Wed, 23 Mar 2011 12:09:50 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p2NG9nPp028702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 23 Mar 2011 12:09:49 -0400 Date: Wed, 23 Mar 2011 21:39:46 +0530 From: Amit Shah Message-ID: <20110323160946.GB28795@amit-x200.redhat.com> References: <20110322163250.GA6426@redhat.com> <20110322165506.GB12508@amit-x200.redhat.com> <20110323095657.GA23292@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110323095657.GA23292@redhat.com> Subject: [Qemu-devel] Re: [PATCH] virtio-serial: don't crash on invalid input List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: qemu-devel@nongnu.org On (Wed) 23 Mar 2011 [11:56:57], Michael S. Tsirkin wrote: > On Tue, Mar 22, 2011 at 10:25:06PM +0530, Amit Shah wrote: > > On (Tue) 22 Mar 2011 [18:32:50], Michael S. Tsirkin wrote: > > > Fix crash on invalid input in virtio-serial. > > > Discovered by code review, untested. > > > @@ -654,6 +654,9 @@ static int virtio_serial_load(QEMUFile *f, void *opaque, int version_id) > > > > > > id = qemu_get_be32(f); > > > port = find_port_by_id(s, id); > > > + if (!port) { > > > + return -EINVAL; > > > + } > > > > Just before this, we matched the ports_map which would bail out if the > > corresponding port isn't avl. in the destination, so this check is > > made redundant. > > You are trusting the remote here, this is a security problem. > A malicious remote will always be able to create arbitrary guest state, > but it should not be able to corrupt the host. I'm still unsure if we'll be able to achieve much if our primary defence goes down: we currently primarily rely on libvirt and selinux to ensure we're in a sane state and any incoming migration is from a properly-initialised qemu instance. If we're receiving data from an untrusted qemu instance or some random sender, we're doomed anyway. Amit