Skip to content
Fencer Intel
medium 5.7

CVE-2010-2811 json

Virtual Desktop Server Manager (VDSM) in Red Hat Enterprise Virtualization (RHEV) 2.2 does not properly accept TCP connections for SSL sess…

published 2010-08-24 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-2815

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

Summary

Virtual Desktop Server Manager (VDSM) in Red Hat Enterprise Virtualization (RHEV) 2.2 does not properly accept TCP connections for SSL sessions, which allows remote attackers to cause a denial of service (daemon outage) via crafted SSL traffic.

Patch / fix

  • rhev-hypervisor RHEL 5 5.5-2.2.6.1.el5_5rhev2_2
  • rhev-hypervisor-pxe RHEL 5 5.5-2.2.6.1.el5_5rhev2_2
  • vdsm22 RHEL 5 4.5-62.14.el5_5rhev2_2
  • vdsm22-cli RHEL 5 4.5-62.14.el5_5rhev2_2

red hat advisories RHSA-2010:0622RHSA-2010:0628

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-2811 updated cvss 2.9

vdsm: SSL accept() blocks on a non-blocking Connection

  • Red Hat Enterprise Virtualization Hypervisor 5 rhev-hypervisor 5.5-2.2.6.1.el5_5rhev2_2, rhev-hypervisor-pxe 5.5-2.2.6.1.el5_5rhev2_2
    fixed: vendor fix RHSA-2010:0622
  • Red Hat RHEV Agents (VDSM) vdsm22 4.5-62.14.el5_5rhev2_2, vdsm22-cli 4.5-62.14.el5_5rhev2_2
    fixed: vendor fix RHSA-2010:0628

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

1.00% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

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.