Skip to content
Fencer Intel
medium 4.4

CVE-2010-2239 json

Red Hat libvirt, possibly 0.6.0 through 0.8.2, creates new images without setting the user-defined backing-store format, which allows guest…

published 2010-08-19 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-2251

cvss
4.4
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

Red Hat libvirt, possibly 0.6.0 through 0.8.2, creates new images without setting the user-defined backing-store format, which allows guest OS users to read arbitrary files on the host OS via unspecified vectors.

Patch / fix

  • libvirt Debian 14, Debian 13, Debian 12 0.8.3-1

debian advisories DEBIAN-CVE-2010-2239

  • libvirt RHEL 5 VIRTUALIZATION 0.6.3-33.el5_5.3
  • libvirt-python RHEL 5 VIRTUALIZATION 0.6.3-33.el5_5.3

red hat advisories RHSA-2010:0615

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-2010-2239 updated cvss 1.5

libvirt: not setting user defined backing store format when creating new image

  • Red Hat Enterprise Linux 5 libvirt
    affected: no fix available
  • Red Hat Enterprise Linux Desktop Multi OS (v. 5 client) libvirt 0.6.3-33.el5_5.3, libvirt-python 0.6.3-33.el5_5.3 Red Hat Enterprise Linux Virtualization (v. 5 server) libvirt 0.6.3-33.el5_5.3, libvirt-python 0.6.3-33.el5_5.3
    fixed: vendor fix RHSA-2010:0615
  • Red Hat Enterprise Linux 6 libvirt, libvirt-client, libvirt-python, libvirt-lock-sanlock
    not affected: vulnerable code not present

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.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.4 AV:L/AC:M/Au:S/C:C/I:N/A:N

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel 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.