The Anatomy of an Exploit
summary
Walks through a real C/x86_64 exploit: a deliberately vulnerable program using gets buffer overflow is compiled, debugged with gdb and objdump, and repeatedly hardened or weakened by toggling ASLR, NX and stack canaries and by binary-patching constants to force “42” missiles. Uses Metasploit pattern_create/offset, strace and hand‑written shellcode (77 then 30 bytes), achieves a live shell via return jump and proves a pipeable exploit works; notes modern defenses push attackers toward return-oriented programming and info‑leaks.
AI-written summary · about
chapters (39)
- 0:00Introduction
- 0:52Patricia Aas
- 1:45The Weird Machine
- 2:35The Weird State
- 4:32The Mental Model
- 5:08Exploit Development
- 5:52Target Program
- 6:18Program
- 7:17CWE
- 7:47Use of inherently dangerous function
- 8:19Happy day scenario
- 8:51Unhappy day scenario
- 10:26Global Thermonuclear War
- 10:38Stack Canary
- 12:49Debug Build
- 13:22Prefer C
- 14:15Debug
- 14:46Stack variables
- 15:01Short string
- 16:15Control
- 16:51Automate
- 17:59Fixing C
- 19:23Stack Buffer Overflow
- 23:52SLR Address Layout
- 25:10Pattern Offset
- 27:03Shellcode
- 27:39Exploit Framework II
- 29:03Code Size
- 29:53STrace
- 30:44Shell Code
- 31:17Shut Sea
- 32:17Inline Assembly
- 32:36Calling Convention
- 36:20Character Buffers
- 36:49Shell
- 37:45Pipe
- 38:04Cheating
- 40:41Weird States
- 47:43deterministically correct
related talks
57mThe Anatomy of an Exploit
22mDemostrating Binary Exploitation
57mReturn Oriented Programming, an introduction
55mHow hacking works
44mDeep Analysis of Exploitable Linux Kernel Vulnerabilities 2017-2019
01h 06mHow hacking works
01h 00m“Secure Coding Best Practices: Your First Line Is The Last Line Of Defense (1 of 2)”
51mExploiting Hardware Glitches And Side Channels In Perfect Software