← Back to Labs

Stack & Heap Memory Corruption Exploits

Step through stack frame overflows, glibc ptmalloc heap Use-After-Free corruption, Return-Oriented Programming (ROP) gadgets, and ASLR/DEP bypasses

NORMAL STACK FRAME: Local buffer allocated, Saved RBP & Saved RIP intactMEMORY MAP: HIGH ADDR [0x7fffffffde30] ↓ LOW ADDR [0x7fffffffde00][0x7fffffffde30] Saved RIP (Return Addr)0x00401142 (main+42)INTACT[0x7fffffffde28] Saved RBP (Frame Ptr)0x7fffffffde50INTACT[0x7fffffffde00] char buf[32] Local Buffer0x00... (32 Bytes)NORMALCPU REGISTERS (AMD64)RIP (Instruction Ptr):0x00401120RSP (Stack Ptr):0x7fffffffde00RDI (Arg 1):0x00000000debtman.dev • Interactive Memory Exploitation & Binary Hardening Visualizer
STEP 1 OF 6

1. Stack Frame Layout & Normal Execution

When a function is called in C, memory is allocated on the call stack for local variables, saved frame pointers (RBP), and the return address (RIP). In normal execution, functions push and pop frames cleanly as they return control to their caller.

Arrow keys to navigate · R to reset

Tap dots to jump to any step

Read the full article →Take the quiz →