Errata and Notes for ShellCoder's Handbook

This is a notebook for working through The ShellCoder's Handbook, 2nd Edition (Anley, Heasman, Linder, Richarte), wherein things that gives one pause as a shellcoding amateur are documented. Hopefully, someone other than me finds this helpful, but it's okay if you are too 31337 to pick up anyting valuable here. Comments, questions, and contributions are more than welcome.

Sunday, April 10, 2011

Chapter 2, "Using an Exploit", pp 31-38 Continued

›
Chapter 2 presents a simple C program that contains a buffer overflow, victim.c: #include <string.h> int main(int argc, char *argv[]) ...
4 comments:
Monday, August 23, 2010

Chapter 2, "Using an Exploit", pp 31-38

›
There are a couple of code examples in chapter 2 that just wouldn't work for me out of the box. Specifically, I'm referring to atta...
2 comments:
Wednesday, June 17, 2009

Chapter 3, "Spawning a Shell," pp 51-58

›
Just a quick note on the assembly listings that start on page 51: I've found this script to be more useful than the stock ASM syntax hi...
Tuesday, June 16, 2009

Chapter 3, "Injectable Shellcode," page 49

›
After the run through of wack.c, a couple pages are devoted to the notion of nuking your nulls and shortening your shellcode. However, there...
Wednesday, June 10, 2009

Chapter 3, "Shellcode," and a slightly buggy wack.c on page 46

›
On page 46, the question is posed, "how do you really know your shellcode is getting run?" The solution presented is to use strace...
3 comments:
Tuesday, May 19, 2009

Using memfetch, page 37

›
This line is somewhat mysterious: memfetch will dump everything in memory for a specific process; simply look through the binary files for t...
8 comments:
Thursday, April 16, 2009

Debian 2.4 Kernel VMWare image ready!

›
I've created a Debian 3.1 (Sarge) VMWare image, featuring the delightfully insecure 2.4 Linux kernel, after several hours of piecing tog...
12 comments:
›
Home
View web version
Powered by Blogger.