Introduction to Information Security ROP – Recitation 5

We’ll start by overviewing the last lecture before the long holiday. We’ll continue with a short summary, and how to use the tools needed to complete the exercise faster

Return Oriented Programming Return oriented programming is a different way to control the flow of EIP in a program Motivation: Write or Execute: as a result of overflows, the first prevention technique is to make: o Executable memory segments read-only o Writeable memory segments Non-Executable. Most slides in this presentation were taken as is from: Return-oriented Programming: Exploitation without Code Injection By Erik Buchanan, Ryan Roemer, Stefan Savage, Hovav Shacham from the University of California, San Diego

Getting started Need control of memory around %esp Rewrite stack: o Buffer overflow on stack o Format string vuln to rewrite stack contents Move stack: o Overwrite saved frame pointer on stack; on leave/ret, move %esp to area under attacker control o Overflow function pointer to a register spring for %esp: o set or modify %esp from an attacker-controlled register o then return

Schematic: return to libc Control hijacking without executing code Avishai Wool, lecture args ret-addr sfp local buf stack exec() printf() “/bin/sh” libc.so

Returning to Code Chunks (aka Gadgets) Instead of working with small “opcodes” and %eip, we now use larger chunks of code and %esp All the “larger chunks” do multiple register manipulations, and we must consider the effect of all of them. Not everything we want is possible directly, so we have to be creative and work around the problem. All chunks end with 0xc3 (RET) We are effectively using a new ‘language’ to code.

Chunk guidelines All chunk ends with 0xc3 Chunks should be as minimal as possible, containing minimum amount of data Chunks are better if they appear in more “stable” and common libraries such as: libc. (and can then be reused for different binaries). Chunks can not contain Junks. o If the CPU can not interpret the junk in the chunk, it will stop the program with illegal instruction exception.

ROP – Machine level Stack pointer (%esp) determines which instruction sequence to fetch & execute o Processor doesn’t automatically increment %esp; — but the “ret” at end of each instruction sequence does

No-op equivalent No-op instruction does nothing but advance %eip o Return-oriented equivalent: o point to return instruction o advances %esp o Useful in nop sled

Loading Immediates Instructions can encode constants Return-oriented equivalent: o Store on the stack; o Pop into register to use

Control flow Ordinary programming: o (Conditionally) set %eip to new value Return-oriented equivalent: o (Conditionally) set %esp to new value

Multiple instruction sequence Sometimes more than one instruction sequence needed o to encode logical unit Example: load from memory into register: o Load address of source word into %eax o Load memory at (%eax) into %ebx

Gadget summary We can write complex shellcode by returning to relevant gadgets. All gadgets end with ret. (0xc3) Gadgets can not contain junk (everything must be interpretable) “JMP” is analogous to finding code that modifies the ESP. We don’t have to maintain the original alignment of code (on x86). Example: o MOV EAX, 0x5DC3 o This is interpreted into: B8 5D C3 o However, o POP EBP o RETN o This is interpreted into: o 5D C3 Using rop_ptrace.py we debug the executable and are able to locate relevant gadgets To have we everything flowing correctly and make sure we are aware of where ESP and EIP are pointing to at all times.

Infosec ROP Tools./rop_ptrace.py./memmap.py./disas_at_va.py

./rop_ptrace.py./rop_ptrace.py o Usage:./rop_ptrace.py [filename] [depth] “OPCODE” rop_ptrace.py helps you by loading the binary into memory, therefore causing the creation of all linked shared objects (SO). The list of libraries can also be shown via shell command ‘ldd filename’. After loading the binary and waiting for the SOs to load it will search for code chunks ending with ROP and then look back until [depth] bytes. rop_ptrace.py then codes and disassembles the chunk rop_ptrace.py uses distorm3 to disassemble and python- ptrace library to debug the executable.

./rop_ptrace.py cont. [rop_ptrace.py example]

./memmap.py Usage:./memmap.py [filename] o Prints the libraries, memories mapped to, and their permissions. Usage:./memmap.py [filename] [string] o Attempts to locate the string within the mapped memory sections. memmap.py uses python-ptrace

./memmap.py cont. [memmap.py example]

./disas_at_va.py cont. disas_at_va.py [filename] [va] [length] o Disassembles [length] number of bytes at virtual address [va] after loading the binary [filename] to memory. Uses python-ptrace and distorm3.