Attacks/Breaches
10/31/2012
07:45 PM
50%
50%

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
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2027
Published: 2015-03-31
eGroupware before 1.8.006.20140217 allows remote attackers to conduct PHP object injection attacks, delete arbitrary files, and possibly execute arbitrary code via the (1) addr_fields or (2) trans parameter to addressbook/csv_import.php, (3) cal_fields or (4) trans parameter to calendar/csv_import.p...

CVE-2014-2830
Published: 2015-03-31
Stack-based buffer overflow in cifskey.c or cifscreds.c in cifs-utils before 6.4, as used in pam_cifscreds, allows remote attackers to have unspecified impact via unknown vectors.

CVE-2014-7876
Published: 2015-03-31
Unspecified vulnerability in HP Integrated Lights-Out (iLO) firmware 2 before 2.27 and 4 before 2.03 and iLO Chassis Management (CM) firmware before 1.30 allows remote attackers to gain privileges, execute arbitrary code, or cause a denial of service via unknown vectors.

CVE-2014-9462
Published: 2015-03-31
The _validaterepo function in sshpeer in Mercurial before 3.2.4 allows remote attackers to execute arbitrary commands via a crafted repository name in a clone command.

CVE-2014-9706
Published: 2015-03-31
The build_index_from_tree function in index.py in Dulwich before 0.9.9 allows remote attackers to execute arbitrary code via a commit with a directory path starting with .git/, which is not properly handled when checking out a working tree.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.