First published: Fri Mar 22 2013(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/Nova | <12.0.0a0 | 12.0.0a0 |
OpenStack Essex | =2012.1 | |
OpenStack Folsom | =2012.2 | |
OpenStack Grizzly | =2012.2 | |
Ubuntu Linux | =11.10 | |
Ubuntu Linux | =12.04 | |
Ubuntu Linux | =12.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-0335 is considered a medium severity vulnerability due to the potential unauthorized access it provides.
To fix CVE-2013-0335, upgrade your OpenStack Nova installation to version 12.0.0a0 or later.
CVE-2013-0335 affects OpenStack Compute (Nova) releases Grizzly, Folsom, and Essex.
Yes, remote authenticated users can exploit CVE-2013-0335 to gain access to a VM using a VNC token.
The impact of CVE-2013-0335 on cloud security includes the risk of unauthorized access to VMs, potentially compromising sensitive data.