Binary Exploitation & Pwn
Bend a running program to your will, one overwritten pointer at a time.
- الوقت المتوقّع
- ساعتان
- الغرف
- غرفتان
- النقاط
- 425 نقطة
- المسجّلون
- كن أول المسجّلين


عن هذا المسار
Memory-corruption is where you stop trusting abstractions and start reasoning about the stack, the registers, and the bytes a program actually runs. This path starts from the very first stack buffer overflow and builds toward defeating real mitigations — reading the binary, controlling the instruction pointer, and reusing existing code to make the program do what you want. Every room ships the binary for analysis and a live service to exploit.
لمن هذا المسار
Developers and security learners ready to go low-level: people comfortable with C and the command line who want to understand exploitation from the ground up.
المتطلّبات المسبقة
A C mental model, comfort on the Linux command line, and a disassembler (Ghidra, radare2, or objdump) plus Python for scripting payloads. No prior exploitation experience required for the first room.
ما الذي ستتمكّن من فعله
- Explain how the call stack stores a function's saved return address
- Overflow a stack buffer to take control of the instruction pointer
- Write a ret2win exploit against a No-PIE binary
- Leak memory and chain a ret2libc / format-string primitive
- Reason about NX, ASLR, stack canaries and when each one matters
المنهج
الوحدة 1 — Smashing the stackاكتملت 0 من 1 غرف
Your first overwritten return address.
الوحدة 2 — Leaks & code reuseاكتملت 0 من 1 غرف
When one bug is only the beginning.