First the Virtualization Security Public Service Announcement:
By now you've no doubt heard that Ryan Smith and Neel Mehta from IBM/ISS X-Force have discovered vulnerabilities in VMware's DHCP implementation that could allow for "...specially crafted packets to gain system-level privileges" and allow an attacker to execute arbitrary code on the system with elevated privileges thereby gaining control of the system.
Further, Dark Reading details that Rafal Wojtczvk (whose last name's spelling is a vulnerability in and of itself!) from McAfee discovered the following vulnerability:
A vulnerability that could allow a guest operating system user with administrative privileges to cause memory corruption in a host process, and potentially execute arbitrary code on the host. Another fix addresses a denial-of-service vulnerability that could allow a guest operating system to cause a host process to become unresponsive or crash.
...and yet another from the Goodfellas Security Research Team:
An additional update, according to the advisory, addresses a security vulnerability that could allow a remote hacker to exploit the library file IntraProcessLogging.dll to overwrite files in a system. It also fixes a similar bug in the library file vielib.dll.
It is important to note that these vulnerabilities have been mitigated by VMWare at the time of this announcement. Further information regarding mitigation of all of these vulnerabilities can be found here.
You can find details regarding these vulnerabilities via the National Vulnerability Database here:
CVE-2007-0061 - The DHCP server in EMC VMware Workstation before 5.5.5 Build 56455 and 6.x before 6.0.1 Build 55017, Player before 1.0.5 Build 56455 and Player 2 before 2.0.1 Build 55017, ACE before 1.0.3 Build 54075 and ACE 2 before 2.0.1 Build 55017, and Server before 1.0.4 Build 56528 allows remote attackers to execute arbitrary code via a malformed packet that triggers "corrupt stack memory.
CVE-2007-0062 - Integer overflow in the DHCP server in EMC VMware Workstation before 5.5.5 Build 56455 and 6.x before 6.0.1 Build 55017, Player before 1.0.5 Build 56455 and Player 2 before 2.0.1 Build 55017, ACE before 1.0.3 Build 54075 and ACE 2 before 2.0.1 Build 55017, and Server before 1.0.4 Build 56528 allows remote attackers to execute arbitrary code via a malformed DHCP packet that triggers a stack-based buffer overflow.
CVE-2007-0063 - Integer underflow in the DHCP server in EMC VMware Workstation before 5.5.5 Build 56455 and 6.x before 6.0.1 Build 55017, Player before 1.0.5 Build 56455 and Player 2 before 2.0.1 Build 55017, ACE before 1.0.3 Build 54075 and ACE 2 before 2.0.1 Build 55017, and Server before 1.0.4 Build 56528 allows remote attackers to execute arbitrary code via a malformed DHCP packet that triggers a stack-based buffer overflow.CVE-2007-4496 - Unspecified vulnerability in EMC VMware Workstation before 5.5.5 Build 56455 and 6.x before 6.0.1 Build 55017, Player before 1.0.5 Build 56455 and Player 2 before 2.0.1 Build 55017, ACE before 1.0.3 Build 54075 and ACE 2 before 2.0.1 Build 55017, and Server before 1.0.4 Build 56528 allows authenticated users with administrative privileges on a guest operating system to corrupt memory and possibly execute arbitrary code on the host operating system via unspecified vectors.
CVE-2007-4155 - Absolute path traversal vulnerability in a certain ActiveX control in vielib.dll in EMC VMware 6.0.0 allows remote attackers to execute arbitrary local programs via a full pathname in the first two arguments to the (1) CreateProcess or (2) CreateProcessEx method.
I am happy to see that VMware moved on these vulnerabilities (I do not have the timeframe of this disclosure and mitigation available.) I am convinced that their security team and product managers truly take this sort of thing seriously.
However, this just goes to show you that as the virtualization platforms enter further-highlighted mainstream adoption, exploitable vulnerabilities will continue to follow as those who follow the money begin to pick up the scent.
This is another phrase that's going to make a me a victim of my own Captain Obvious Award, but it seems like we've been fighting this premise for too long now. I recognize that this is not the first set of security vulnerabilities we've seen from VMware, but I'm going to highlight them for a reason.
It seems that due to a lack of well-articulated vulnerabilities that extended beyond theoretical assertions or POC's, the sensationalism of research such as Blue Pill has desensitized folks to the emerging realities of virtualization platform attack surfaces.
I've blogged about this over the last year and a half, with the latest found here and an interview here. It's really just an awareness campaign. One I'm more than willing to wage given the stakes. If that makes me the noisy canary in the coal mine, so be it.
These very real examples are why I feel it's ludicrous to take seriously any comments that suggest by generalization that virtualized environments are "more secure" by design; it's software, just like anything else, and it's going to be vulnerable.
I'm not trying to signal that the sky is falling, just the opposite. I do, however, want to make sure we bring these issues to your attention.
Happy Patching!
/Hoff