Apr 26, 2012 (07:04 AM EDT)
VMware Breached, More Hypervisor Source Code To Come
Read the Original Article at InformationWeek
Is your hypervisor safe?
Hypervisors--such as VMware ESXi and Xen--provide the platform on which virtualized guest operating systems run, and are therefore a core component of any business's virtual infrastructure. But they're also a potential security weak point. A 2010 study from IBM, notably, found that 35% of all vulnerabilities in a virtualized environment could be traced to the hypervisor.
Those vulnerabilities are cause for concern in the wake of VMware's Monday confirmation that source code dating to 2003 and 2004 had been publicly released by a hacker billing himself as Hardcore Charlie. Furthermore, he said the release was a "sneak peak" of the 300 MB of VMware source code he said is in his possession, which he said will be publicly released May 5.
Iain Mulholland, director of the VMware Security Response Center, said in a Monday blog post that the company's security team had confirmed that a file containing VMware ESX source code had been published. He promised that VMware would update its customers as it learned more.
[ Defense gets you only so far. Learn Why Security Teams Need To Play More Offense. ]
VMware now ships a more lightweight, embedded version of ESX, dubbed ESXi, on new servers. Both ESX and ESXi are "bare-metal embedded hypervisors," meaning they run directly on server hardware. Might Hardcore Charlie's public look into the inner workings of the VMware hypervisor create security repercussions for ESXi customers, for example if hackers were able to identify exploitable zero-day vulnerabilities in the ESX code?
Multiple security researchers contacted for this story declined to comment, with one saying that he'd first need to see the stolen source code to understand the potential threat. But one hypervisor security worry has been "escape to hypervisor" attacks. No such attacks have yet been seen in the wild. But security experts predict they will happen in the future, and would allow an attacker to escape from a given virtualized machine and potentially access any other virtual machine running on the same server.
VMware, however, is downplaying any security threats that might result from the source code disclosure. "The fact that the source code may have been publicly shared does not necessarily mean that there is any increased risk to VMware customers," Mulholland said. "VMware proactively shares its source code and interfaces with other industry participants to enable the broad virtualization ecosystem today." He also confirmed to Threatpost that some of the documents leaked by Hardcore Charlie appeared to be source code review documents, which would have been used to help describe to VMware insiders, as well as with business partners.
Charlie said he obtained the VMware kernel source code via March attacks against China Electronics Import & Export Corporation (CEIEC). He said he'd also attacked--and still had access to--China North Industries Corporation (Norinco), WanBao Mining, Ivanho, and PetroVietnam. Earlier this month, he released a preview of stolen information via Pastebin, as well as images of multiple documents, some of which appear to be Chinese intercepts of U.S. military transportation documents pertaining to Afghanistan.
But CEIEC released a statement denying its systems had been breached, saying that "the information reported is totally groundless, highly subjective, and defamatory." The company also said that it "reserves the right to take legal action against the relevant responsible individuals and institutions."
Charlie, however, told Threatpost via IRC (Internet relay chat) that he breached CEIEC by first stealing hundreds of thousands of encrypted credentials for Web-based email accounts at Sina.com. He said he then reached out to hacker Yama Tough--who released Symantec source code in January--to help crack the credentials. At that point, he and a group of hackers began looking for accounts of interest.
Charlie promised that a full-scale document dump, involving at least 1 TB of data, would also occur on May 5, including a "complete CEIEC stash of documents." He said that while they were still reviewing the documents' contents, they'd also made a number of interesting discoveries. "We want to make it clear that CEIEC is engaged in a criminal activity with Ukraine and Russian officials as of supplying Ukraine and Russia with U.S. Army information for the terrorists," he said in the Pastebin post. "In Ukraine Chinese security services enforce illegal copper mine deals through corrupted KGHMPM [KGHM (Shanghai) Copper Trading Company] officials and in Russia through Gazprom subsidiary companies."
The preview release, as well as promise of more to come, shows that even after the arrests of multiple alleged LulzSec and Anonymous participants, the practice of "doxing"--obtaining and releasing internal company and government agency documents--remains alive and well. In fact, a "hola lulz" aside in Charlie's Pastebin post makes an overt nod to previous doxers.
InformationWeek is conducting a survey to determine what's important to you when you're choosing vendors of security information and event management (SIEM) products as well as how the vendors are actually doing against those criteria. Upon completion of our survey, you will be eligible to enter a drawing to receive an 16-GB Apple iPad. Take our Security Information And Event Management Vendor Evaluation Survey now. Survey ends April 27.