A return-to-libc ("lib-C") attack overwrites a return address stored in this structure.
Hardware-enforced control-flow integrity requires a "shadow" version of this structure. Cowan et al. introduced a tool to "guard" this structure by changing how a program compiles. Canaries may be placed in this structure to detect and prevent tampering. The "W xor ("ex-or") X" protocol and the ProPolice extension to GCC both attempt to prevent this structure from being used to store shellcode. "Scribbling" and "trashing" this structure are described in a paper by the programmer Aleph One entitled "Smashing [this structure] For Fun And Profit." A return-to-libc ("lib-C") attack overwrites a return address stored in this structure. Like a buffer, this structure may be vulnerable to an infinitely-recursive "overflow" attack. For 10 points, name this last-in first-out structure in which frames are "pushed" and "popped" during function calls.
Hardware-enforced control-flow integrity requires a "shadow" version of this structure.
call stack [or the stack; or run-time stack; or execution stack; or control stack; or function stack; prompt on buffer until “buffer” is read] &lt;Other Science (Computer Science)&gt;