http://www.openasthra.com/c-tidbits/bad-standard-apis/ C/C++ Programming Blog Sun, 06 Jul 2008 20:21:44 +0000 http://wordpress.org/?v=2.3.1 http://www.openasthra.com/c-tidbits/bad-standard-apis/#comment-40 Buffer Overruns - part1 Wed, 17 Jan 2007 08:50:10 +0000 http://www.openasthra.com/c-tidbits/bad-standard-apis/#comment-40 [...] Buffer Overruns/Overflows are typically caused by trusting input data to a function that is external and is unchecked. Most of the times, this is unintentionally invoked by bad sloppy code. However, when done intentionally by a hacker, this can cause havoc. Some of the most common, buffer overrun prone functions include strcpy, memcpy, strcat etc. (bad standard APIs are explained in another post) In unintentional buffer overruns/overflows, this mostly results in writing to memory not owned by your processes address space. In such cases this would end, in an access violation or a core dump, causing the program to be aborted in most cases. However, these buffer overruns can be exploited to run arbitrary code on the machine, even code that is injected in by the attacker.  Before going deep into this overruns let us understand the program executable layout, this helps us in better understanding of the overurns. [...] […] Buffer Overruns/Overflows are typically caused by trusting input data to a function that is external and is unchecked. Most of the times, this is unintentionally invoked by bad sloppy code. However, when done intentionally by a hacker, this can cause havoc. Some of the most common, buffer overrun prone functions include strcpy, memcpy, strcat etc. (bad standard APIs are explained in another post) In unintentional buffer overruns/overflows, this mostly results in writing to memory not owned by your processes address space. In such cases this would end, in an access violation or a core dump, causing the program to be aborted in most cases. However, these buffer overruns can be exploited to run arbitrary code on the machine, even code that is injected in by the attacker.  Before going deep into this overruns let us understand the program executable layout, this helps us in better understanding of the overurns. […]

]]>