Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Buffer overflow protection
open-in-new
<p>Buffer overflow protection is any of various techniques used during software development to enhance the security of executable programs by detecting <a href="/facts/Buffer_overflow/uMFduL4B">buffer overflows</a> on <a href="/facts/Call_stack/1sMt713v">stack</a>-allocated variables, and preventing them from causing program misbehavior or from becoming serious <a href="/facts/Computer_security/7E5dIy7G">security</a> vulnerabilities. A stack buffer overflow occurs when a program writes to a memory address on the program's call stack outside of the intended data structure, which is usually a fixed-length buffer. Stack buffer overflow bugs are caused when a program writes more data to a buffer located on the stack than what is actually allocated for that buffer. This almost always results in corruption of adjacent data on the stack, which could lead to program crashes, incorrect operation, or security issues. </p><p>Typically, buffer overflow protection modifies the organization of stack-allocated data so it includes a <i><a href="/facts/Stack_canary/s7zC9na6">canary</a></i> value that, when destroyed by a stack buffer overflow, shows that a buffer preceding it in memory has been overflowed. By verifying the canary value, execution of the affected program can be terminated, preventing it from misbehaving or from allowing an attacker to take control over it. Other buffer overflow protection techniques include <i><a href="/facts/Bounds_checking/vnAjD4Lp">bounds checking</a></i>, which checks accesses to each allocated block of memory so they cannot go beyond the actually allocated space, and <i>tagging</i>, which ensures that memory allocated for storing data cannot contain executable code. </p><p>Overfilling a buffer allocated on the stack is more likely to influence program execution than overfilling a buffer on the <a href="/facts/Dynamic_memory_allocation/vthLkUpz">heap</a> because the stack contains the return addresses for all active function calls. However, similar implementation-specific protections also exist against heap-based overflows. </p><p>There are several implementations of buffer overflow protection, including those for the <a href="/facts/GNU_Compiler_Collection/t07jh01k">GNU Compiler Collection</a>, <a href="/facts/LLVM/nPmcspQN">LLVM</a>, <a href="/facts/Microsoft_Visual_Studio/omNe6Lej">Microsoft Visual Studio</a>, and other compilers. </p>