CVE-2013-0335

Openstack nova: vnc proxy can connect to the wrong vm

Published Mar 22, 2013 CVSS 3.1 · 7.6 High EPSS 2.1% KEV · Not listed
Description
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.

Remediation

Vendor Workaround

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2013-0022 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.
Github GHSA Github GHSA GHSA-qfp8-hfqx-c79c OpenStack Compute Nova Unauthorised access to arbitrary VM using VNC token from deleted VM
Ubuntu USN Ubuntu USN USN-1771-1 OpenStack Nova vulnerabilities
History
Type Values Removed Values Added
Title nova: VNC proxy can connect to the wrong VM Openstack nova: vnc proxy can connect to the wrong vm
Weaknesses CWE-613
CPEs cpe:/a:redhat:openstack:13
cpe:/a:redhat:openstack:16.2
cpe:/a:redhat:openstack:17.1
cpe:/a:redhat:openstack:18.0
References
Metrics cvssV3_1

{'score': 7.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Jul 31, 2026, 2:23 PM
Reserved
Dec 6, 2012, 12:00 AM
Status
Modified
Published
Mar 22, 2013, 9:55 PM
Modified
Jul 31, 2026, 3:16 PM
Severity
Moderate
Public date
Feb 26, 2013, 12:00 AM