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-2013-2184
Published: 2015-03-27
Movable Type before 5.2.6 does not properly use the Storable::thaw function, which allows remote attackers to execute arbitrary code via the comment_state parameter.

CVE-2014-3619
Published: 2015-03-27
The __socket_proto_state_machine function in GlusterFS 3.5 allows remote attackers to cause a denial of service (infinite loop) via a "00000000" fragment header.

CVE-2014-8121
Published: 2015-03-27
DB_LOOKUP in nss_files/files-XXX.c in the Name Service Switch (NSS) in GNU C Library (aka glibc or libc6) 2.21 and earlier does not properly check if a file is open, which allows remote attackers to cause a denial of service (infinite loop) by performing a look-up while the database is iterated over...

CVE-2014-9712
Published: 2015-03-27
Websense TRITON V-Series appliances before 7.8.3 Hotfix 03 and 7.8.4 before Hotfix 01 allows remote administrators to read arbitrary files and obtain passwords via a crafted path.

CVE-2015-2157
Published: 2015-03-27
The (1) ssh2_load_userkey and (2) ssh2_save_userkey functions in PuTTY 0.51 through 0.63 do not properly wipe SSH-2 private keys from memory, which allows local users to obtain sensitive information by reading the memory.

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.