dbcve.org
FedoraOperating system · Fedoraproject

CVE-2007-1320

HIGH · 7.2 CVSS v2.0 Published 2007-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges 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
Multiple heap-based buffer overflows in the cirrus_invalidate_region function in the Cirrus VGA extension in QEMU 0.8.2, as used in Xen and possibly other products, might allow local users to execute arbitrary code via unspecified vectors related to "attempting to mark non-existent regions as dirty," aka the "bitblt" heap overflow.

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 · moderate confidence

Heap-based buffer overflow in QEMU's Cirrus VGA extension (cirrus_invalidate_region function) allowing local privilege escalation via manipulated bitblt (bit block transfer) operations that attempt to mark non-existent memory regions as dirty.

MitigationApply vendor patches for QEMU 0.8.2 and affected Xen versions; restrict local user access to virtualization hosts until patched; consider disabling Cirrus VGA emulation if not required.

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
FedoraOperating system
Affected:= 8= 9
Debian LinuxOperating system
Affected:= 3.1= 4.0
QemuApplication
Affected:= 0.8.2
Fedora CoreOperating system
Affected:= 6
OpensuseOperating system
Affected:= 11.0= 11.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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/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. Identify QEMU version
    Run 'qemu --version' or check the package version with 'rpm -q qemu' (RPM-based) or 'dpkg -l qemu' (Debian-based)
    Affected if Version equals 0.8.2 specifically, or falls within the affected product version ranges (Fedora 8-9, Fedora Core 6, Debian 3.1-4.0, openSUSE 11.0-11.1)
  2. Verify Cirrus VGA emulation is in use
    Check the QEMU command line arguments or VM configuration for '-vga cirrus' or examine the VM's displayed hardware (the virtual graphics adapter shows as 'Cirrus Logic GD5446' in Windows Device Manager or 'Cirrus' in Linux lspci output)
    Affected if The VM is configured with Cirrus VGA emulation (vga=cirrus or similar) rather than stdvga, vmware, or virtio
  3. Confirm VM is running on affected host
    Identify the virtualization host and determine if it runs the vulnerable QEMU version. For Xen hosts, check if 'xm list' or 'xl list' shows the domain0 or check the hypervisor version with 'xm version' or 'xl version'
    Affected if The virtualization host uses the vulnerable QEMU version and the guest uses Cirrus VGA

You are affected if your system runs QEMU 0.8.2 (or an affected Fedora/Debian/openSUSE version) and the virtual machine is configured to use Cirrus VGA emulation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for QEMU 0.8.2 and affected Xen versions; restrict local user access to virtualization hosts until patched; consider disabling Cirrus VGA emulation if not required.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1320 — 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-2007-1320 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