In the Stack Guard approach to solving the buffer overflow problem, the compiler inserts a canary value
Fantastic news! We've Found the answer you've been seeking!
Question:
In the Stack Guard approach to solving the buffer overflow problem, the compiler inserts a canary value on the memory location before the return address in the stack The canary value is randomly generated When there is a return from the function call, the compiler checks if the canary value has been overwritten or not Do you think that this approach would work If yes, please explain why it works if not, please give a counterexample?
Related Book For
Posted Date: