Skip to content
Fencer Intel
low 2.1

CVE-2010-2223 json

Virtual Desktop Server Manager (VDSM) in Red Hat Enterprise Virtualization Hypervisor (aka RHEV-H or rhev-hypervisor) before 5.5-2.2 does n…

published 16y ago modified 4mo ago also EUVD-2010-2239

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

Summary

Virtual Desktop Server Manager (VDSM) in Red Hat Enterprise Virtualization Hypervisor (aka RHEV-H or rhev-hypervisor) before 5.5-2.2 does not properly perform VM post-zeroing after the removal of a virtual machine's data, which allows guest OS users to obtain sensitive information by examining the disk blocks associated with a deleted virtual machine.

Patch / fix

  • rhev-hypervisor RHEL 5 5.5-2.2.4.2.el5rhev
  • rhev-hypervisor-pxe RHEL 5 5.5-2.2.4.2.el5rhev
  • vdsm22 RHEL 5 4.5-62.el5rhev
  • vdsm22-cli RHEL 5 4.5-62.el5rhev

red hat advisories RHSA-2010:0476RHSA-2010:0473

Is CVE-2010-2223 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2223 updated cvss 2.1

vdsm: missing VM post-zeroing after removal

  • Red Hat Enterprise Virtualization Hypervisor 5 rhev-hypervisor 5.5-2.2.4.2.el5rhev, rhev-hypervisor-pxe 5.5-2.2.4.2.el5rhev
    fixed: vendor fix RHSA-2010:0476
  • Red Hat RHEV Agents (VDSM) vdsm22 4.5-62.el5rhev, vdsm22-cli 4.5-62.el5rhev
    fixed: vendor fix RHSA-2010:0473

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

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/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.