CVE-2010-0429: Medium severity qspice vulnerability

Published Feb 26, 2010
·
Updated

Izik Eidus found a bug in QEMU that allows priviledged guest user to force QEMU process on the host to issue free() and/or malloc() calls at addresses controlled by the guest user. The bug is in QXL/libspice code.

Other sources

libspice, as used in QEMU-KVM in the Hypervisor (aka rhev-hypervisor) in Red Hat Enterprise Virtualization (RHEV) 2.2 and qspice 0.3.0, does not properly restrict the addresses upon which memory-management actions are performed, which allows guest OS users to cause a denial of service (guest OS crash) or possibly gain privileges via unspecified vectors.

MITRE

Affected Software

2 affected components
redhat Qspice=0.3.0
redhat Enterprise Virtualization=2.2

Event History

Feb 26, 2010
Data Sourced
12:11 PM
DescriptionSeverityAffected Software
Aug 24, 2010
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2010-0429?

CVE-2010-0429 is classified as a high severity vulnerability due to its potential impact on system integrity.

2

How do I fix CVE-2010-0429?

To mitigate CVE-2010-0429, you should upgrade to an unaffected version of QEMU and the related libspice components.

3

Who is affected by CVE-2010-0429?

CVE-2010-0429 affects users running QEMU with the QXL/libspice code on Red Hat Enterprise Virtualization and Qspice 0.3.0.

4

What are the potential risks associated with CVE-2010-0429?

The risks associated with CVE-2010-0429 include potential privilege escalation and denial of service due to uncontrolled memory management.

5

When was CVE-2010-0429 reported?

CVE-2010-0429 was reported in early 2010, highlighting a critical vulnerability in virtualized environments.

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