what does stack and heap overflow exploit means

Question

what does this stack and heap over flow exploit mean

Answer 1

An example of Stack-based exploitation: (implementation defined or possibly undefined, nevertheless interesting!)

Just look at the output: http://www.ideone.com/A3vlY

Also note the runtime-error!

I'm particularly trying to do this:

• By overwriting the return address in a stack frame. Once the function returns, execution will resume at the return address as specified by the attacker, usually a user input filled buffer.

From wikipedia's Stack-based exploitation bullet points

This example possibly demonstrates the above bullet-point quoted from wikipedia, giving you an interesting starting point of what Stack-based exploitation could mean. Sort of impetus for thought!

Answer 2

Wikipedia has a pretty good overview of these types of exploits: http://en.wikipedia.org/wiki/Buffer_overflow

Answer 3

For a real world example of this, check out this other Stack Overflow question:

Writing to pointer out of bounds after malloc() not causing error