A type of exploitation in programming in which a set buffer is created in a program and a user has the advantage of overflowing that buffers set limit to allow the user to execute arbitrary code by overwriting a memory block, held for the buffer.
#include <stdio.h>
int main(int argc, char **argv) {
buffer300; //set buffer to store 300 bytes
if(argc<=2) {
printf("usage: %s <data to put in buffer>", argv0);
}else{
memset(buffer, argv1); //add 2nd argument (the data) into the buffer
printf("%s",buffer); //print data that resides in the buffer
}
if more than 300 bytes are put into the buffer, it will cause a segmentation fault causing a buffer overflow.
int main(int argc, char **argv) {
buffer300; //set buffer to store 300 bytes
if(argc<=2) {
printf("usage: %s <data to put in buffer>", argv0);
}else{
memset(buffer, argv1); //add 2nd argument (the data) into the buffer
printf("%s",buffer); //print data that resides in the buffer
}
if more than 300 bytes are put into the buffer, it will cause a segmentation fault causing a buffer overflow.
by atomix April 25, 2004
Computer term: When code in the stack-buffer overflows into another application's process. Can cause applications to crash or execute malicious code.
This client is vulnerable to buffer overflow exploits.
by Alex January 15, 2004
Euphemism for an immediate need to defecate or urinate. Also synonymous for having already done so in public.
"I'm about to have a buffer overflow. brb!"
by bembleton August 14, 2007