Binary Exploitation Workshop

From Chaosdorf Wiki
Binary Exploitation Workshop
Segmentation fault (core dumped)
Art Meet-Up
Relevant? Yes
Binary Exploitation Workshop obsolete
Binary Exploitation Workshop
Ort Chaosdorf
Beteiligt ilias

Exploitation Workshop
Binary Exploitation Workshop
Art Workshop
Datum 2019-08-05
Start 13:00
Host ilias
Relevant? Yes

Please read[edit | edit source]

Option 1:

   - Virtual machine software (VMWare, VirtualBox etc...)
   - Ubuntu 16.04 guest system(with binutils, gdb, python2.7, and the pwntools python module)
   - your C editor of choice

Option 2:

   This is the prefered method.
   - Install VirtualBox
   - Install Vagrant (wrapper for VirtualBox)
   - download this Vagrantfile
   - run vagrant up && vagrant ssh
   That will automatically create the ubuntuVM, install all the packages we need and setup a nice debugging environment.
   Another plus is that you will have exactly the same setup as me so debugging any problems is going to be easier.
   NOTE: The installation can take up to an hour.

This Workshop is for beginners. Beginner as in new to binary exploitation not as in new to low level stuff, c and assembly.

We'll try to briefly cover the usage of:

  • the pwntools python module
  • radare2 dissassembler (mostly for static analysis)
  • gdb (for dynamic analysis)
  • automated ROP-gadget finders

The focus will be:

  • to learn about vulnerable C functions
  • to learn how simple exploits used to be
  • to learn what the GOT is
  • to learn what mitigations have been introduced in modern systems
  • to learn how to use ROP (return oriented programming) to bypass many exploit mitigations

I will bring some binaries that we can attempt exploit. The goal is for every participant to be able to write a stackpivot->malloc->memcpy->mprotect ropchain to execute shellcode.

Prerequisites[edit | edit source]

As a participant, you should at least know:

   - C
   - Intel x86_64 assembly
   - the x86_64 calling convention
   Bonus points for knowing the layout of a process in memory and where each section gets loaded into ;D

Participants (please add your name!)[edit | edit source]

Resolving technical issues[edit | edit source]

try: $ wget -q -O- | sh

Resources[edit | edit source]