CVE-2014-0144: Buffer Overflow

Published Mar 21, 2014
·
Updated

QEMU before 2.0.0 block drivers for CLOOP, QCOW2 version 2 and various other image formats are vulnerable to potential memory corruptions, integer/buffer overflows or crash caused by missing input validations which could allow a remote user to execute arbitrary code on the host with the privileges of the QEMU process.

Other sources

Qemu block drivers for CLOOP, QCOW2 version 2 and various other image formats are vulnerable to potential memory corruptions, integer/buffer overflows or crash caused by missing input validations.

An user able to alter the Qemu disk image files loaded by a guest could use this flaw to crash the Qemu instance resulting in DoS or corrupt QEMU process memory on the host, which could potentially result in arbitrary code execution on the host with the privileges of the QEMU process.

Upstream fixes: --------------- qcow2: Validate active L1 table offset and size -> http://git.qemu.org/?p=qemu.git;a=commit;h=2d51c32c4b511db8bb9e58208f1e2c25e4c06c85

qcow2: Validate snapshot table offset/size -> http://git.qemu.org/?p=qemu.git;a=commit;h=ce48f2f441ca98885267af6fd636a7cb804ee646

qcow2: Check refcount table size -> http://git.qemu.org/?p=qemu.git;a=commit;h=5dab2faddc8eaa1fb1abdbe2f502001fc13a1b21

qcow2: Check backingfileoffset -> http://git.qemu.org/?p=qemu.git;a=commit;h=a1b3955c9415b1e767c130a2f59fee6aa28e575b

qcow2: Check headerlength -> http://git.qemu.org/?p=qemu.git;a=commit;h=24342f2cae47d03911e346fe1e520b00dc2818e0

curl: check data size before memcpy to local buffer -> http://git.qemu.org/?p=qemu.git;a=commit;h=6d4b9e55fc625514a38d27cff4b9933f617fa7dc

vdi: add bounds checks for blocksinimage and disksize -> http://git.qemu.org/?p=qemu.git;a=commit;h=63fa06dc978f3669dbfd9443b33cde9e2a7f4b41

vpc/vhd: add bounds check for maxtableentries -> http://git.qemu.org/?p=qemu.git;a=commit;h=97f1c45c6f456572e5b504b8614e4a69e23b8e3a

block/cloop: refuse images with bogus offsets -> http://git.qemu.org/?p=qemu.git;a=commit;h=f56b9bc3ae20fc93815b34aa022be919941406ce

block/cloop: refuse images with huge offsets arrays -> http://git.qemu.org/?p=qemu.git;a=commit;h=7b103b36d6ef3b11827c203d3a793bf7da50ecd6

block/cloop: validate blocksize header field -> http://git.qemu.org/?p=qemu.git;a=commit;h=d65f97a82c4ed48374a764c769d4ba1ea9724e97

Red Hat

Affected Software

9 affected components
Qemu Qemu<2.0.0
redhat Virtualization=3.0
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Eus=6.5
redhat Enterprise Linux Openstack Platform=5
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server Aus=6.5
redhat Enterprise Linux Server Tus=6.5
redhat Enterprise Linux Workstation=6.0

Event History

Mar 21, 2014
Data Sourced
09:25 AM
DescriptionSeverityAffected Software
Feb 11, 2020
CVE Published
via MITRE·02:13 AM
Data Sourced
via MITRE·02:13 AM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2014-0144?

CVE-2014-0144 has a critical severity due to potential remote code execution vulnerabilities.

2

How do I fix CVE-2014-0144?

To fix CVE-2014-0144, upgrade QEMU to version 2.0.0 or later.

3

What vulnerabilities are associated with CVE-2014-0144?

CVE-2014-0144 is associated with memory corruption, integer overflows, and buffer overflows affecting various block drivers.

4

Which QEMU versions are affected by CVE-2014-0144?

All QEMU versions prior to 2.0.0 are affected by CVE-2014-0144.

5

How can CVE-2014-0144 affect my system?

CVE-2014-0144 can allow remote users to execute arbitrary code on the host system, compromising system security.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203