Uploaded December 2019 | Updated September 2026, 2 weeks ago

---

I often get questions about exploits that do not work, and sometimes the problem is the shellcode. This video shows how to test the bytes, use INT3 breakpoints, step through shellcode in GDB, and produce a useful debugging report.

LEARN ON HEXTREE (ad)
Learn hacking on Hextree: hextree.io
Watch this video and more on Hextree: app.hextree.io/courses/yt-basic-buffer-overflows/common-exploitation-pitfalls
Join the Hextree Discord: discord.gg/xgQpCQCpvy

Haxember 2019 Playlist: youtube.com/playlist?list=PLhixgUqwRTjzTvVyL_8H-DJBf8VT3uiu2

CHAPTERS
00:00 - Testing shellcode in a minimal program
01:07 - Checking execution with an INT3 trap
01:44 - Investigating the segmentation fault in GDB
03:18 - Comparing memory with the intended raw bytes
04:39 - Finding the missing echo escape flag
05:31 - Stepping through corrupted shellcode
07:12 - Finding the shellcode entry with a backtrace
07:45 - Breaking before the call into shellcode
08:43 - Building a useful test case when asking for help

SUPPORT
Per video: patreon.com/join/liveoverflow
Per month: youtube.com/channel/UClcE-kVhqyiHCcjYwcpfj9w/join
Buy my handwriting font (ad): shop.liveoverflow.com

WATCH, FOLLOW & READ
Second channel: youtube.com/LiveUnderflow
Twitch: twitch.tv/LiveOverflow
Twitter: twitter.com/LiveOverflow
Instagram: instagram.com/LiveOverflow
TikTok: tiktok.com/@liveoverflow_
LiveOverflow blog: liveoverflow.com
Hextree blog (ad): hextree.io/blog

#BufferOverflow #BinaryExploitation #LiveOverflow

(ad) LiveOverflow YouTube channel is supported by advertisement and product placement.