CVE-2007-1320 json
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…
published 2007-05-02 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1317
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- qemu Debian 14, Debian 13, Debian 12 0.9.0-2
debian advisories DEBIAN-CVE-2007-1320
- xen RHEL 5 VIRTUALIZATION, RHEL 5 3.0.3-25.0.4.el5
- xen-libs RHEL 5 3.0.3-25.0.4.el5
red hat advisories RHSA-2007:0323
- xen openSUSE Tumbleweed 4.15.1_01-1.2
opensuse advisories openSUSE-SU-2024:11520-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2007-1320 updated
xen/qemu Cirrus LGD-54XX "bitblt" Heap Overflow
-
Red Hat Enterprise Linux (v. 5 server) xen 3.0.3-25.0.4.el5, xen-libs 3.0.3-25.0.4.el5 Red Hat Enterprise Linux Desktop (v. 5 client) xen 3.0.3-25.0.4.el5, xen-libs 3.0.3-25.0.4.el5 Red Hat Enterprise Linux Desktop Multi OS (v. 5 client) xen 3.0.3-25.0.4.el5, xen-libs 3.0.3-25.0.4.el5 Red Hat Enterprise Linux Virtualization (v. 5 server) xen 3.0.3-25.0.4.el5, xen-libs 3.0.3-25.0.4.el5fixed: vendor fix RHSA-2007:0323
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
mandriva.com
/security/advisories?name=MDKSA-2007:203
vendor-advisory, third-party-advisory
-
redhat.com
/archives/fedora-package-announce/2008-May/msg00706.html
vendor-advisory, third-party-advisory
-
redhat.com
/archives/fedora-package-announce/2008-May/msg00935.html
vendor-advisory, third-party-advisory
-
debian.org
/security/2007/dsa-1284
vendor-advisory, third-party-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2008:162
vendor-advisory, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2009-01/msg00004.html
vendor-advisory, mailing-list, third-party-advisory
-
redhat.com
/support/errata/RHSA-2007-0323.html
vendor-advisory, third-party-advisory
-
redhat.com
/archives/fedora-package-announce/2007-October/msg00082.html
vendor-advisory, third-party-advisory
-
debian.org
/security/2007/dsa-1384
vendor-advisory, third-party-advisory
-
securityfocus.com
/bid/23731
vdb-entry, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10315
vdb-entry, signature, third-party-advisory
-
osvdb.org
/35494
vdb-entry, broken-link
-
secunia.com
/advisories/27047
third-party-advisory
-
secunia.com
/advisories/25073
third-party-advisory
-
taviso.decsystem.org
/virtsec.pdf
technical-description, third-party-advisory
-
secunia.com
/advisories/27486
third-party-advisory
-
secunia.com
/advisories/27085
third-party-advisory
-
secunia.com
/advisories/30413
third-party-advisory
-
secunia.com
/advisories/33568
third-party-advisory
-
vupen.com
/english/advisories/2007/1597
vdb-entry, third-party-advisory
-
secunia.com
/advisories/27103
third-party-advisory
-
secunia.com
/advisories/29129
third-party-advisory
-
secunia.com
/advisories/25095
third-party-advisory
Sources
- CVE List CVE-2007-1320
- NVD CVE-2007-1320
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.