# Game Rules¶

## Overview¶

In each lab (every week), you are asked to solve a set of challenges (typically 10 challenges except for the first two weeks). In each challenge, you have to submit three things, namely, a flag, the exploit, and its write-up via scoreboard: the flag you got from the challenge (see below), the exploit that you wrote, and the write-up that summarizes how you formulate the exploit (see below).

A flag is a 512-byte hex string (like below) and you can find it in /proc/flag once you properly initialize the distributed VM.

$cat /proc/flag CB25682B33EF8BF23545A767562A1D5AA33C88EEACC1AE562D950CB9F1E5725D 864725DB51460902ECBD52BA4CBED86A10F3A98A35F6FB71871019702A0E9199 5BC59332C390A3C27D0EC2CE85BC13E956A6027E3171352F90467A8C12346D9A 2A26EE914B3078ED031FDB14BB6224C3D743D79A733FB49EB4E9C1F383CF810E F6841EE935FE2DA2C57DB4804B6823884B36AE62B08848486918C120E4C2AA94 E1D3F8A6E9E2251AC39E5F37971FB07DFF839E0BC1C4E6C1D4A24E0948F8751B 25BFFE854CD84A8D8E28814398FF192CD9AD37150D83DA872E944DF1552F97DD 1649508E5B9E356925F0762AAF53A4683F48AD4B88C0C863FB03DC5B9C5F77A3 9B3156D4E91ED42B76BDDD3962B39BEAF3520BEC297EC89250F10776A869C2C0 5EAA97231C1F0780B25958FA950816D4DD94C448DF99EC3813183BD20C3006F7 D0825569DAEC45534A355094E4F1A5CC2760F45ED6E8B586DCBA23B27B26E19C 99DDA9B1D17983D1138E3EB7B25BEB927FC34B1FCADEC408CBE7CA04D3E27E39 466D051D4DCA562F292AA623884E9D34BA790E6E46F400F1F6B410F2DDCB8D29 1B0AEBF92CBBA24CB37B8C407F036873C65F568DE58BFD6246ABBABC7D06ADF2 E5A86F2C76E927CF741E8E2B75CAA6530B313EAB80F1C0B7E6B8B22E6D9703C1 A0591DD166168C791A26D32AE6ED3730BA1185B53517436721EE0E3458DB6EF4  Your job is to read this flag by exploiting the distributed challenges. ## Taking actions¶ 1. Download and install Virtualbox/Vagrant Note: Ubuntu users may want to use the following commands to install Virtualbox and Vagrant [host]$ sudo apt-get install virtualbox
[host] $sudo apt-get install vagrant  1. Add guest OS and run the VM # download a 64-bit VM [host]$ vagrant box add ubuntu/trusty64
box: URL: https://atlas.hashicorp.com/ubuntu/trusty64
==> box: Adding box 'ubuntu/trusty64' (v20160822.0.0) for provider: virtualbox
==> box: Successfully added box 'ubuntu/trusty64' (v20160822.0.0) for 'virtualbox'!

# move to your working directory
[host] $mkdir seclab [host]$ cd seclab

# initialize the VM
[host] $vagrant init ubuntu/trusty64 A Vagrantfile has been placed in this directory. You are now ready to vagrant up your first virtual environment! Please read the comments in the Vagrantfile as well as documentation on vagrantup.com for more information on using Vagrant. # launch! [host]$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
...

[host] $vagrant ssh Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-93-generic x86_64) ... vagrant@vagrant-ubuntu-trusty-64:~$

1. Once you have the VM up and running, let’s initialize your VM for this course:
# in the VM, install git/gcc
[vm] $sudo apt-get update [vm]$ sudo apt-get install git
[vm] $sudo apt-get install gcc-multilib # it's time for setting up your environment # # WARNING. # You should use 'cs6265' # [vm]$ git clone git://tc.gtisc.gatech.edu/seclab-pub cs6265
...
[vm] $cd cs6265 [vm]$ ls
README    ; general info
bin/      ; scripts
lab/lab01 ; binaries for lab01
lab/lab02 ; ditto
...

# initialize your working environment (only need to be done once)
[vm] $./bin/init  1. To do labs: # to do lab1 [vm]$ git pull
[vm] $cd lab01 [vm]$ cat README
[vm] $cd bomblab1_01 ... # NOTE. test your environment setup [vm]$ bin/checkin


Feel free to ask for any help on Piazza, or at the office hours if you meet any trouble during the setup.

## General rule¶

If not specified (e.g., first two weeks), we will follow the scoring rules stated below:

• Approximately 10 challenges every week.
• 20 points (flag) x 1.0 (write-up/exploit) = 20 points (each challenge).
• 200 points (20 points x 10 challenges) are the maximum points, in theory.
• Bonus: first and second bloods (i.e., fastest solvers) will get 10 and 5 bonus points in each challenge.
• Late policy: 50% of the original points (only within one week past the due).

## Write-up Sample¶

In this problem, ebp and ret value are protected by gsstack. while
debugging, you can see all ebp and ret values are keep tracking and
storing somewhere. However, when you make an input large enough, you
will see that a function pointer will be overwritten. And the
overwritten value will be store in EAX and make it jump at
<main+96>. I put my shellcode as env, get the address, and put it. In
my case, the function pointer(0x08048b0a at 0xbffff654) was
overwritten. So we could learn, we could jump using the weakpoint even
though the stackshiled is working on.

\$(python -c 'print "\x90"*108+"\x90"*44+"\x87\xf8\xff\xbf"+"\x90"*50')