As such, remember that this article focuses on identifying programming and code habits and patterns – familiarizing ourselves with VMWare’s development team traits, and potential vulnerabilities. Several potential security vulnerabilities were discovered however, due to incomplete source code they cannot be verified until the next article. The source had a multitude of bugs which may or may not have had a security impact since then. The code was analyzed for a variety of common vulnerabilities including, but not limited to, stack and heap overflows, double free bugs, and string or file truncation amongst other problems. In our next installment, we’ll test the potential bugs identified here against the latest version of ESX.
Functions and data types remain undefined in certain areas, and entire headers are missing in others. Its important to keep in mind that because the leak was only partial, there is no current way to fully rely on the leaked code to identify vulnerabilities. In this installment (Part 1), we’ll focus on how VmWare works, common programming mistakes in the released version, and a bit of our auditing methodology. It is our belief that by examining the existing potential for vulnerablity within the newly leaked code base and cross-referencing it with the current version of ESX, we can determine the true impact of the breach.
Due to the age of the code released, one can infer that either one of VMWare’s archive servers could be recently compromised, or that the code may have been released by a disgruntled employee. It is difficult to determine which, however it is important to note that none of the files within the leaked archive ended abruptly, indicating that it is in fact possible that the attacker may have a much more complete copy. The source code was seemingly either only partially obtained or only partially disclosed by the attacker. Following due-diligence to determine the impact, the source code has been analyzed and audited for a number of common vulnerabilities. The VMware ESX source code (from 2004 according to VMware, Inc.) was partially leaked on November 4, 2012.
0 kommentar(er)
