Introduction

The previous chapter focused on writing exploits, particularly format string attacks and race conditions. In this chapter, we will focus on exploiting overflow-related vulnerabilities, including stack overflows, heap corruption, and integer bugs.

Buffer overflows and similar software bugs that have security implications exist largely because software development firms don t believe that making software more secure will positively affect the bottom line. Rapid release cycles and the priority of time to market over anything else will never end. Few large software development organizations publicly claim to develop secure software. Most that announce this usually receive immediate negative press, at least in the security community, which not only contradicts their claims but puts the company in a less than flattering light. Due to politics, misunderstandings, and the availability of a large code base, some organizations are consistently targeted by bug researchers seeking glory in the press. Companies with few public software bugs achieve this mainly by staying under the radar.

Interestingly enough, multiple organizations that develop security software also have been subject to the negative press of having a vulnerability in their security software. Even developers who are aware of the security implications of code can make errors. For instance, on one occasion, a well-known security researcher released a software tool to the community for free use. Later, a vulnerability was found in that software. This is understandable, since everyone makes mistakes and bugs are often hard to spot. What is more ironic is that when the security researcher released a...