Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
cs-465:project-8-buffer-overflow [2016/11/08 11:18]
seamons
cs-465:project-8-buffer-overflow [2017/11/11 17:03]
seamons
Line 1: Line 1:
 = Project 8 (Buffer Overflow) = = Project 8 (Buffer Overflow) =
- 
-UNDER CONSTRUCTION FALL 2016 - DO NOT BEGIN YET 
  
 == Objectives == == Objectives ==
Line 10: Line 8:
 == Resources == == Resources ==
  
-The CS department has prepared a VM for each of you to be able to use on the lab machines or your own machine. You need to be connected to the CS network to download the actual VM. [[http://wiki.cs.byu.edu/​_media/cs-465/tousestudentvmlab8.pdf|Instructions]]+The CS department has prepared a VM for each of you to be able to use on the lab machines or your own machine. You need to be connected to the CS network to download the actual VM. [[https://docs.google.com/​a/​cs.byu.edu/document/d/14MlNZmbqkx8jzibNOcpAGWZ3bk36qw1XcLIRjCoqG08/​edit?​usp=sharing|Instructions]]
  
 For tips on how to use GDB, [https://​gist.github.com/​ThaWeatherman/​6912322 here] is a document detailing some of the more useful and important commands. Ignore the comments on the Bomb lab: it may become a lab later in the semester but you don't have to worry about it now. For tips on how to use GDB, [https://​gist.github.com/​ThaWeatherman/​6912322 here] is a document detailing some of the more useful and important commands. Ignore the comments on the Bomb lab: it may become a lab later in the semester but you don't have to worry about it now.
Line 20: Line 18:
 Compile the program and run it in the debugger, breaking somewhere in function senior. Compile the program and run it in the debugger, breaking somewhere in function senior.
 Print out all of the stack activation frames, and label as many memory locations as you can.  Print out all of the stack activation frames, and label as many memory locations as you can. 
 +
 +Not all the stack locations will be labeled. Extra space may be allocated on the stack that is set to uninitialized values that already existing in memory. Be sure to label the following elements for all four functions.
 You should be able to identify 1) return addresses, 2) saved frame pointers (ebp), 3) local variables, 4) function arguments. You should be able to identify 1) return addresses, 2) saved frame pointers (ebp), 3) local variables, 4) function arguments.
-You may print out a hard copy, write on it to label all the items, and turn in the hard copy. You may also submit ​your result electronically.+Use the "info frame" gdb command to compare the information you labeled with what the debugger reports is in each stack frame. 
 +You may print out a hard copy, write on it to label all the items, and turn in a scan of the hard copy. You may also create ​your result electronically. Make it easy for the TAs to grade.
 * Link to [http://​faculty.cs.byu.edu/​~seamons/​examine_stack.c examine_stack.c] * Link to [http://​faculty.cs.byu.edu/​~seamons/​examine_stack.c examine_stack.c]
 * Compile the program with the -m32 compiler option. We will use a 32-bit program for simplicity. * Compile the program with the -m32 compiler option. We will use a 32-bit program for simplicity.
Line 48: Line 49:
 For this option you can practice your buffer overflow skills against the Carnegie Mellon buflab. This lab is a part of EE 324 as well. Currently we do not have a project description posted. However the one for EE 324 is [http://​ece324web.groups.et.byu.net/​Labs/​buflab/​buflab.pdf here] and it is the same as what you will be doing here. However please note that you cannot work in teams, despite what that spec says. For your cookie provide your NetID. This lab can only be done on CS lab machines (not SPICE machines like the spec says). You can SSH into them if you don't want to go into the labs.  For this option you can practice your buffer overflow skills against the Carnegie Mellon buflab. This lab is a part of EE 324 as well. Currently we do not have a project description posted. However the one for EE 324 is [http://​ece324web.groups.et.byu.net/​Labs/​buflab/​buflab.pdf here] and it is the same as what you will be doing here. However please note that you cannot work in teams, despite what that spec says. For your cookie provide your NetID. This lab can only be done on CS lab machines (not SPICE machines like the spec says). You can SSH into them if you don't want to go into the labs. 
  
-Get your bomb [http://padme.cs.byu.edu:​18213 ​here]. See the results board [http://padme.cs.byu.edu:18213/scoreboard here].+Get your bomb [http://bombs.sebulba.cs.byu.edu/​bombs ​here]. See the results board [http://bombs.sebulba.cs.byu.edu/​scoreboard here].
  
  
cs-465/project-8-buffer-overflow.txt · Last modified: 2017/11/11 17:10 by seamons
Back to top
CC Attribution-Share Alike 4.0 International
chimeric.de = chi`s home Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0