# CVE-2010-0430: Memory corruption in n/a

> Guest OS users can read or write arbitrary QEMU memory by manipulating Cairo memory mappings, impacting virtualization security.

- **Severity:** High 7.4 (`AV:A/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Dec 2013
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5g9q-h772-m2pq

## What is CVE-2010-0430?

CVE-2010-0430 is a high-severity memory corruption vulnerability in n/a, published on 27 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-0430?

It affects 1 product.


Products: Redhat Enterprise Virtualization Hypervisor.

## How do I fix CVE-2010-0430?

Upgrade to a fixed version.

## Is CVE-2010-0430 being exploited?

There is no known exploitation of CVE-2010-0430 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2010-2223](https://insights.sbomify.com/CVE-2010-2223/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0430 and fix it if it is affected.

What it is: CVE-2010-0430 is a high-severity memory corruption vulnerability in n/a, published on 27 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0430 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-0430/ (Markdown: https://insights.sbomify.com/CVE-2010-0430/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0430
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0430
- OSV: https://osv.dev/vulnerability/CVE-2010-0430

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-0430/
Summaries are generated and may contain mistakes; the official description above is the record.