dbcve.org
Enterprise Virtualization HypervisorApplication · Redhat

CVE-2010-0430

HIGH · 7.4 CVSS v2.0 Published 2013-12-27
Fix available
A fix is available. Upgrade to after 5.4-2.1 or later.
See remediation →
76/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
libspice, as used in QEMU-KVM in Red Hat Enterprise Virtualization Hypervisor (aka RHEV-H or rhev-hypervisor) before 5.5-2.2 and possibly other products, allows guest OS users to read from or write to arbitrary QEMU memory by modifying the address that is used by Cairo for memory mappings.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a memory corruption vulnerability in libspice (used with QEMU-KVM) where guest OS users can modify the address used by Cairo for memory mappings, allowing read/write access to arbitrary QEMU memory locations. This enables a malicious guest to escape its isolation and interact with the host's QEMU process memory.

MitigationUpdate the libspice library and QEMU-KVM to versions that include the fix (RHEV-H 5.5-2.2 or later). In environments where updates are not feasible, consider disabling Spice display redirection or restricting VM network access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise Virtualization HypervisorApplication
Affected:<= 5.4-2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
M
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:A/AC:M/Au:S/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check RHEV-H hypervisor version
    Run 'rpm -q redhat-release' or inspect /etc/redhat-release to obtain the installed Red Hat Enterprise Virtualization Hypervisor version
    Affected if Version is 5.4-2.1 or earlier (vulnerable)
  2. Verify Spice display is enabled
    Examine the VM configuration or QEMU process command line arguments for the presence of Spice display parameters (such as -spice or display=spice)
    Affected if Spice display redirection is active for the virtual machine
  3. Confirm libspice library is present
    Run 'rpm -q libspice-server' or 'rpm -q spice-server' to determine if the Spice server library is installed on the hypervisor
    Affected if libspice library is installed alongside the vulnerable hypervisor version

Environment is affected if running RHEV-H version 5.4-2.1 or earlier AND Spice display redirection is enabled for at least one virtual machine

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 5.4-2.1
Interim mitigation

Update the libspice library and QEMU-KVM to versions that include the fix (RHEV-H 5.5-2.2 or later). In environments where updates are not feasible, consider disabling Spice display redirection or restricting VM network access.

Fix this in Enterprise Virtualization Hypervisor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0430 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data