Openstack nova: vnc proxy can connect to the wrong vm
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.6epss 2.1%
exploitation probability
2.1%top 20% of all CVEs
observed exploitation
nono source reports it
OpenStack Compute (Nova) Grizzly, Folsom (2012.2), and Essex (2012.1) allows remote authenticated users to gain access to a VM in opportunistic circumstances by using the VNC token for a deleted VM that was bound to the same VNC port.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
Affected products
Red Hat · OpenStack Folsom for RHEL 6Red Hat · Red Hat OpenStack Platform 13 (Queens)Red Hat · Red Hat OpenStack Platform 16.2Red Hat · Red Hat OpenStack Platform 17.1Red Hat · Red Hat OpenStack Platform 18.0References
http://rhn.redhat.com/errata/RHSA-2013-0709.htmlhttps://access.redhat.com/errata/RHSA-2013:0709https://access.redhat.com/security/cve/CVE-2013-0335https://bugs.launchpad.net/nova/+bug/1125378http://secunia.com/advisories/52337http://secunia.com/advisories/52728https://github.com/advisories/GHSA-qfp8-hfqx-c79chttps://review.openstack.org/#/c/22086/https://review.openstack.org/#/c/22758https://review.openstack.org/#/c/22872/http://www.openwall.com/lists/oss-security/2013/02/26/7http://www.osvdb.org/90657