Xen Security Advisory CVE-2015-5154 / XSA-138 QEMU heap overflow flaw while processing certain ATAPI commands. *** EMBARGOED UNTIL 2015-07-27 12:00 UTC *** ISSUE DESCRIPTION ================= The QEMU security team has predisclosed the following advisory: A heap overflow flaw was found in the way QEMU's IDE subsystem handled I/O buffer access while processing certain ATAPI commands. A privileged guest user in a guest with CDROM drive enabled could potentially use this flaw to execute arbitrary code on the host with the privileges of the host's QEMU process corresponding to the guest. IMPACT ====== An HVM guest which has access to an emulated IDE CDROM device (e.g. with a device with "devtype=cdrom", or the "cdrom" convenience alias, in the VBD configuration) can exploit this vulnerability to take over the qemu process elevating its privilege to that of the qemu process. VULNERABLE SYSTEMS ================== All Xen systems running x86 HVM guests without stubdomains which have been configured with an emulated CD-ROM driver model are vulnerable. Systems using qemu-dm stubdomain device models (for example, by specifying "device_model_stubdomain_override=1" in xl's domain configuration files) are NOT vulnerable. Both the traditional "qemu-xen" or upstream qemu device models are potentially vulnerable. Systems running only PV guests are NOT vulnerable. ARM systems are NOT vulnerable. MITIGATION ========== Avoiding the use of emulated CD-ROM devices altogether, by not specifying such devices in the domain configuration, will avoid this issue. Enabling stubdomains will mitigate this issue, by reducing the escalation to only those privileges accorded to the service domain. qemu-dm stubdomains are only available with the traditional "qemu-xen" version. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. xsa138-qemut-{1,2}.patch qemu-xen-traditional, Xen unstable, Xen 4.5.x, Xen 4.4.x, Xen 4.3.x, Xen 4.2.x xsa138-qemuu-{1,2,3}.patch qemu-upstream, xen unstable, Xen 4.5.x, Xen 4.4.x, Xen 4.3.x xsa138-qemuu-{1,3}.patch qemu-upstream, Xen 4.2.x NOTE: xsa138-qemuu-2.patch is not required for Xen 4.2.x. $ sha256sum xsa138*.patch 7e385455379d88658b8ab0d4c1effffe9af21fff2e1dc0fe51cacc779afc83a4 xsa138-qemut-1.patch c9a89082e36a0646a6fe002c6892d966d415d11ad5cfdcfea7e9c8d7a3f1316c xsa138-qemut-2.patch a076808f543c82aeac2f0239a4a46d9baadcd4e4b0a2f9ae7ded99cf59cffde6 xsa138-qemuu-1.patch ed16dca7d2c179d0931d6e2503264d6593547a803eb3f08f6db7fff2127509a9 xsa138-qemuu-2.patch 090bdec00ede1f0ace1af52833038a74971e060d0c176b42bfca08511d36c644 xsa138-qemuu-3.patch $ DEPLOYMENT DURING EMBARGO ========================= Deployment of patches or mitigations is NOT permitted (except on systems used and administered only by organisations which are members of the Xen Project Security Issues Predisclosure List). Specifically, deployment on public cloud systems is NOT permitted. The decision not to permit deployment was made by the group that, at their discretion, disclosed the issue to the Xen Project Security Team. Deployment is permitted only AFTER the embargo ends. (Note: this during-embargo deployment notice is retained in post-embargo publicly released Xen Project advisories, even though it is then no longer applicable. This is to enable the community to have oversight of the Xen Project Security Team's decisionmaking.) For more information about permissible uses of embargoed information, consult the Xen Project community's agreed Security Policy: http://www.xenproject.org/security-policy.html
This is likely relevant for Qemu as well
Issue is now public
(In reply to Kristian Fiskerstrand from comment #1) > This is likely relevant for Qemu as well Its purely a qemu issue and not specific to Xen itself.
*** Bug 556050 has been marked as a duplicate of this bug. ***
addressed in qemu-2.3.0-r4
+*xen-tools-4.5.1-r2 (30 Jul 2015) +*xen-tools-4.2.5-r9 (30 Jul 2015) + + 30 Jul 2015; Yixun Lan <dlan@gentoo.org> +xen-tools-4.2.5-r9.ebuild, + +xen-tools-4.5.1-r2.ebuild: + security bump, bug 555532; bump ovmf to 2015/06/29, commit + cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd Arches, please test and mark stable: =app-emulation/xen-tools-4.2.5-r9 Target keywords Both : "amd64 x86" =app-emulation/xen-tools-4.5.1-r2 Target keywords Only: "amd64"
amd64 stable
x86 stable. Maintainer(s), please cleanup. Security, please add it to the existing request, or file a new one.
+ 31 Jul 2015; Yixun Lan <dlan@gentoo.org> -xen-tools-4.2.5-r8.ebuild, + -xen-tools-4.5.1-r1.ebuild: + clean vulnerable ebuild due to security bug #555532
Arches and Maintainer(s), Thank you for your work. Added to an existing GLSA Request.
This issue was resolved and addressed in GLSA 201604-03 at https://security.gentoo.org/glsa/201604-03 by GLSA coordinator Yury German (BlueKnight).
