Skip to content
Fencer Intel
medium 4.4

CVE-2011-1773 json

virt-v2v before 0.8.4 does not preserve the VNC console password when converting a guest, which allows local users to bypass the intended V…

published 2014-02-08 12 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1771

cvss
4.4
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 41%
public exploits
0
none known

Summary

virt-v2v before 0.8.4 does not preserve the VNC console password when converting a guest, which allows local users to bypass the intended VNC authentication by connecting without a password.

Patch / fix

  • virt-v2v RHEL 6 0.8.3-5.el6

red hat advisories RHSA-2011:1615

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-2011-1773 updated cvss 3.7

virt-v2v: vnc password protection is missing after vm conversion

  • Red Hat Enterprise Linux 5 virt-v2v
    affected: no fix available
  • Red Hat Enterprise Linux Desktop (v. 6) virt-v2v 0.8.3-5.el6 Red Hat Enterprise Linux HPC Node (v. 6) virt-v2v 0.8.3-5.el6 Red Hat Enterprise Linux Server (v. 6) virt-v2v 0.8.3-5.el6 Red Hat Enterprise Linux Workstation (v. 6) virt-v2v 0.8.3-5.el6
    fixed: vendor fix RHSA-2011:1615

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

Exploits and checks

  • git.fedorahosted.org https://git.fedorahosted.org/cgit/virt-v2v.git/commit/?id=7e9393129116699d1228bb02b9f65b78584582c1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-255 Credentials Management Errors

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.