Attacks/Breaches
10/31/2012
07:45 PM
Connect Directly
RSS
E-Mail
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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.