CIPHERFLARE

Stack Buffer Overflows - EIP Control to Code Execution

Lab Setup Three things need to be sorted on the Windows lab machine before any of this works cleanly. Antivirus off. Shellcode and exploit scripts will be flagged and quarantined before they ever run. Real-time protection, tamper protection, SmartScreen, all of it needs to go. Turn off tamper protection first, then real-time protection. If you do it the other way around, Defender re-enables itself. ASLR disabled system-wide. Windows randomizes module base addresses by default, which means every time the program runs, the modules load at different addresses. For foundational exploit development you need those addresses to stay the same between runs so any gadget address you hardcode in a payload is still valid the next time. This registry key forces that: ...

April 30, 2026 · 14 min · Awagat Dhungana
CIPHERFLARE

Stack Frames - The Foundation of Every Stack Overflow

Where Everything Starts Before you write a single byte of shellcode, before you talk about ROP chains or DEP bypasses, there is one mental model you need to have locked in cold. The stack frame. Every stack-based exploit ever written comes down to the same thing: you overflow a buffer, you overwrite a return address, and when the function returns, the CPU jumps somewhere you control. That’s it. The techniques that come later are just clever ways of working around defenses layered on top of that same primitive. ...

April 30, 2026 · 9 min · Awagat Dhungana