With the release of Windows 8 scheduled for October 26, Windows
security is on our mind. Windows is one of the most widely used operating
systems in the world, making it a lucrative target for exploit developers and
malware authors. In previous versions of Windows, many security features were
introduced, including ASLR, DEP and pointer encodings. Microsoft utilized
software development lifecycle and threat modeling to ensure it was delivering
a secure operating system to its users; however,
many of previous Windows security exploits were the result of developers
overlooking the proper implementation of protocol standards. Supplementing the detailed analysis made available by Microsoft, in this blog post,
we share additional analysis of one of these exploits and highlight a short
list of additional exploits that were the result of poor security validation.
Microsoft implemented many initiatives focused on developing code
that was secure from exploitation of vulnerabilities, but unfortunately, many
zero-day vulnerabilities were reported in Windows 2008 and Windows 7.
Let’s dive
into the analysis of one zero-day CVE-2011-0654 which was reported on February
14, 2011, for Windows 7 and 2008 servers to understand the factor that seems
to have been missed to ensure the safety of Windows.