0x1000 · Area
Vulnerability Classes
Memory-safety bugs fall into a small number of recurring classes. Each guide here shows the vulnerable pattern in a few lines of C, explains why it corrupts memory, and then shows the fix, the compiler warning or sanitizer that catches it, and the mitigation that limits the damage.
Guides in this area
Why writing past a stack buffer is dangerous, the C patterns that cause it, how compilers and sanitizers catch it, and the fixes and mitigations that contain it.
How heap memory bugs corrupt allocator metadata and object state, why use-after-free is so dangerous, and the allocator hardening, sanitizers and ownership rules that stop them.
How integer overflow, truncation and signedness errors turn into memory corruption, why user-controlled format strings are dangerous, and the checks and warnings that prevent both.
Other areas
Memory Fundamentals
Stack, heap, ELF segments and calling conventions: the terrain every bug lives on.
Exploit Mitigations
Canaries, NX/DEP, ASLR/PIE, RELRO, FORTIFY_SOURCE, CFI, CET and PAC, and how to verify them.
Finding Bugs
AddressSanitizer, UBSan and coverage-guided fuzzing with libFuzzer and AFL++.
Crash Triage
Read signals, backtraces, sanitizer reports and core dumps, and decide what to fix first.
Secure Coding
Memory-safe languages, safer C++ and a realistic migration strategy.
Learning Path
A staged, legal path from C and assembly to CTF pwn challenges and security careers.