Attacks/Breaches
10/31/2012
07:45 PM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Automation Demands Tighter VM Security

Plan to let hypervisors spin up new virtual machines on their own? Then you'd better lock them down.

From a security standpoint, basic server hypervisors have a lot of intrinsic strength. They work at a very low level within a given piece of hardware. They're hardened and task-specific, and the code base is relatively small. And it's a good thing, because the hypervisor enjoys a privileged degree of access to guest operating systems, especially via OS-native virtual machine tools, which allow the hypervisor all sorts of power. Compromising the hypervisor gives complete and total access to all of the data structures that comprise the system itself. But when we asked about hypervisor security, only 64% of respondents to our survey cited concern about this issue. That leaves a staggering 36%--greater than one-third of respondents--who have their heads in the sand. If a system runs code, it can be compromised, and if that code is running everywhere, there's a huge incentive to break it. There have been no fewer than 10 major hypervisor vulnerabilities disclosed this year alone, affecting a variety of platforms. Exploits range from remote code execution vulnerabilities (the most severe) to denial of service, and while VMware has yet to disclose a remote code execution vulnerability, it's only a matter of time. Earlier this year, for example, outdated source code for VMware's ESX hypervisor was posted.

We still see companies with a long way to go to integrate hypervisor awareness into their overall security mandates. The good news is that vendors have been preparing for this eventuality for some time, as we discuss in our full report. Also, about half of survey respondents (48%) have a hypervisor-aware security product in place. An additional 32% plan to adopt one.

Go to the main story:
A Shaky Virtual Stack

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: LOL.
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3154
Published: 2014-04-17
DistUpgrade/DistUpgradeViewKDE.py in Update Manager before 1:0.87.31.1, 1:0.134.x before 1:0.134.11.1, 1:0.142.x before 1:0.142.23.1, 1:0.150.x before 1:0.150.5.1, and 1:0.152.x before 1:0.152.25.5 does not properly create temporary files, which allows local users to obtain the XAUTHORITY file conte...

CVE-2013-2143
Published: 2014-04-17
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the update_roles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.

CVE-2014-0036
Published: 2014-04-17
The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

CVE-2014-0054
Published: 2014-04-17
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External ...

CVE-2014-0071
Published: 2014-04-17
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

Best of the Web