Generally with a buffer overrun, you're trying to put executable code in, and get it to a spot where it'll be run, allowing you to do further stuff. Here is a

Generally with a buffer overrun, you're trying to put executable code in, and get it to a spot where it'll be run, allowing you to do further stuff. Here is a canonical old article on one type of buffer overflow: http://www.phrack.org/issues/49/14.html#article http://www.phrack.org/issues/49/14.html#article (The webp one, iirc, is not a stack buffer overflow, but rather a heap, but that'll give you a general sense of what's going on, even if that article is a bit ... dated)