CVE-2013-0335GHSA-QFP8-HFQX-C79CPYSEC-2013-43
Openstack nova: vnc proxy can connect to the wrong vm
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 12.0.0a0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- openstack-nova
Version range not reported
- redhat-user-workloads/openstack-nova-compute
Version range not reported
- redhat-user-workloads/openstack-nova-compute-ironic
Version range not reported
- redhat-user-workloads/openstack-nova-compute
Version range not reported
- redhat-user-workloads/openstack-nova-compute-ironic
Version range not reported
- redhat-user-workloads/openstack-nova-compute
Version range not reported
- redhat-user-workloads/openstack-nova-compute-ironic
Version range not reported
- redhat-user-workloads/openstack-nova-compute
Version range not reported
- novaPyPI
fixed in 12.0.0a0