[kernel-xen] Fwd: Xen Security Advisory 25 (CVE-2012-4544) - Xen domain builder Out-of-memory due to malicious kernel/ramdisk
netwiz at crc.id.au
Sat Oct 27 04:14:52 EST 2012
Just pushed Xen 4.2.0-4 to the repos to address this.
Email: netwiz at crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
-------- Original Message --------
Subject: Xen Security Advisory 25 (CVE-2012-4544) - Xen domain builder
Out-of-memory due to malicious kernel/ramdisk
Date: Fri, 26 Oct 2012 11:01:47 +0000
From: Xen.org security team <security at xen.org>
To: xen-announce at lists.xen.org, xen-devel at lists.xen.org,
xen-users at lists.xen.org, oss-security at lists.openwall.com
CC: Xen.org security team <security at xen.org>
-----BEGIN PGP SIGNED MESSAGE-----
Xen Security Advisory CVE-2012-4544 / XSA-25
Xen domain builder Out-of-memory due to malicious kernel/ramdisk
The Xen PV domain builder contained no validation of the size of the
supplied kernel or ramdisk either before or after decompression. This
could cause the toolstack to consume all available RAM in the domain
running the domain builder.
A malicious guest administrator who can supply a kernel or ramdisk can
exhaust memory in domain 0 leading to a denial of service attack.
All versions of Xen are vulnerable.
Running only trusted kernels and ramdisks will avoid this
Using pvgrub also avoids this vulnerability since the builder will run
in guest context. (nb: use of pygrub *is* vulnerable).
Running only HVM guests will avoid this vulnerability.
CVE-2012-2625 covers a bug in pygrub which caused that process to
consume excessive amount of memory under similar circumstances to the
This was fixed in xen-unstable (and the fix inherited by Xen 4.2.x) in
revision 25589:60f09d1ab1fe but not called out as a security problem.
This fix is also included, where relevant, in the patches below.
Applying the appropriate attached patch resolves this issue, including
the related pygrub fix where neccesary.
xsa25-unstable.patch Xen unstable
xsa25-4.2.patch Xen 4.2.x
xsa25-4.1.patch Xen 4.1.x
$ sha256sum xsa25*.patch
Note that these patches impose a new size limit of 1Gby on both the
compressed and uncompressed sizes of ramdisks. On some systems it may
be desirable to relax these limits and risk virtual address or memory
exhaustion in the toolstack. This can be achieved by setting
XC_DOM_DECOMPRESS_MAX to the desired limit (in bytes). This can be
done by building with "APPEND_CFLAGS=-DXC_DOM_DECOMPRESS_MAX=<limit>"
or by editing tools/libxc/xc_dom.h directly.
NOTE REGARDING LACK OF EMBARGO
These issues have already been discussed in public in various places,
and http://bugs.debian.org/688125. This advisory is therefore not
subject to an embargo.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4965 bytes
Desc: S/MIME Cryptographic Signature
More information about the kernel-xen