From ${URL} : Correct post load checks: 1. dev->setup_len == sizeof(dev->data_buf) seems fine, no need to fail migration 2. When state is DATA, passing index > len will cause memcpy with negative length, resulting in heap overflow An user able to alter the savevm data (either on the disk or over the wire during migration) could use this flaw to to corrupt QEMU process memory on the (destination) host, which could potentially result in arbitrary code execution on the host with the privileges of the QEMU process. Upstream fix: ------------- -> http://article.gmane.org/gmane.comp.emulators.qemu/272092 @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
upstream has merged the fix now
qemu-2.0.0-r1 has the fixes
(In reply to SpanKY from comment #2) > qemu-2.0.0-r1 has the fixes Are we ready for stabilization?
Arches, please test and mark stable: =app-emulation/qemu-2.0.0-r1 Target keywords : "amd64 x86"
I suppose we also should do the deps!? Are there any opinions about other versions than the following? =sys-cluster/glusterfs-3.5.1 =sys-infiniband/librdmacm-1.0.18 =sys-infiniband/libibverbs-1.1.7 =net-fs/libnfs-1.9.5
(In reply to Andreas Schürch from comment #5) > I suppose we also should do the deps!? > Are there any opinions about other versions than the following? > =sys-cluster/glusterfs-3.5.1 > =sys-infiniband/librdmacm-1.0.18 > =sys-infiniband/libibverbs-1.1.7 > =net-fs/libnfs-1.9.5 I guess we could stable-mask the infiniband IUSE.
amd64 stable
x86 stable. Maintainer(s), please cleanup. Security, please add it to the existing request, or file a new one.
Arches, Thank you for your work Maintainer(s), please drop the vulnerable version(s). Added to existing GLSA Request
cleanup done
This issue was resolved and addressed in GLSA 201408-17 at http://security.gentoo.org/glsa/glsa-201408-17.xml by GLSA coordinator Kristian Fiskerstrand (K_F).
CVE-2014-3461 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-3461): hw/usb/bus.c in QEMU 1.6.2 allows remote attackers to execute arbitrary code via crafted savevm data, which triggers a heap-based buffer overflow, related to "USB post load checks."
