Sitemap
All pages on the site.
Home
Map
Guides
- KASLR, KPTI and Modern Kernel Defenses
- Kernel Exploitation: From a Bug to root
- ret2usr, SMEP and SMAP
- The Mitigation Stack: Which Defenses, In Order
- Bypassing DEP on Windows with ROP
- Windows Flow-Integrity Mitigations: CFG and CET
- SEH Overwrites: Hijacking Windows Exceptions
- ARM64 Exploitation: the Link Register and ret2win
- PAC and BTI: ARM's Answer to Code Reuse
- ROP on ARM64: Gadgets and the Link Register
- one-gadget: One Address to a Shell
- ret2dlresolve: Resolving a Symbol Without a Leak
- Seccomp Sandboxes and the open-read-write Chain
- File-Structure Attacks: Hijacking a FILE Object
- Information Leaks: Defeating ASLR and Canaries
- ret2csu: Borrowing the Runtime's Universal Gadget
- SROP: Exploiting with a Fake Signal Frame
- Stack Pivoting: Relocating the ROP Chain
- Format-String Bugs: Arbitrary Read and Write
- Hijacking the GOT: Redirecting a libc Call
- Heap Exploitation: tcache and Use-After-Free
- Hijacking Control Flow: the ret2win Technique
- Returning into libc: the ret2libc Technique
- Building a ROP Chain Step by Step
- A Binary Exploitation Learning Path Through CTFs
- Memory-Safe Languages and a Realistic Migration Strategy
- Coverage-Guided Fuzzing with libFuzzer and AFL++
- Reading Crash Reports: Signals, Backtraces and Core Dumps
- AddressSanitizer, UBSan and Friends: A Practical Guide
- Control-Flow Integrity: CFI, Intel CET and Arm PAC/BTI
- Stack Canaries, NX, ASLR/PIE, RELRO and FORTIFY_SOURCE
- Integer Overflows and Format-String Bugs, Explained
- Heap Overflows, Use-After-Free and Double Free
- Stack Buffer Overflows Explained for Defenders
- How a Process Lays Out Memory: Stack, Heap and ELF Segments