CNIT 127 Ch 4: Introduction to format string bugs
1 like727 views
The document provides an overview of format string vulnerabilities, detailing how these bugs can lead to memory exploitation and arbitrary code execution. It explains several exploitation techniques, including manipulation of the stack and the Global Offset Table (GOT) to gain control of program execution. Additionally, the document discusses countermeasures and the usage of tools like GDB for debugging and testing vulnerabilities.
![Buffer Overflow
• This code is obviously stupid
char name[10];
strcpy(name, "Rumplestiltskin");
• C just does it, without complaining](https://image.slidesharecdn.com/127-ch4-180210161806/85/CNIT-127-Ch-4-Introduction-to-format-string-bugs-8-320.jpg)
CNIT 127 Ch 4: Introduction to format string bugs
- 1. CNIT 127: Exploit Development Ch 4: Introduction to Format String Bugs Updated 2-10-18
- 3. Data Interpretation • RAM contains bytes • The same byte can be interpreted as – An integer – A character – Part of an instruction – Part of an address – Part of a string – Many, many more...
- 4. Format String Controls Output
- 6. Most Important for Us • %x Hexadecimal • %8x Hexadecimal padded to 8 chars • %10x Hexadecimal padded to 10 chars • %100x Hexadecimal padded to 100 chars
- 8. Buffer Overflow • This code is obviously stupid char name[10]; strcpy(name, "Rumplestiltskin"); • C just does it, without complaining
- 9. Format String Without Arguments • printf("%x.%x.%x.%x"); – There are no arguments to print! – Should give an error message – Instead, C just pulls the next 4 values from the stack and prints them out – Can read memory on the stack – Information disclosure vulnerability
- 10. Format String Controlled by Attacker
- 11. Explanation • %x.%x.%x.%x -- read 4 words from stack • %n.%n.%n.%n -- write 4 numbers to RAM locations from the stack
- 12. %n Format String • %n writes the number of characters printed so far • To the memory location pointed to by the parameter • Can write to arbitrary RAM locations • Easy DoS • Possible remote code execution
- 13. printf Family • Format string bugs affect a whole family of functions
- 14. Countermeasures
- 15. Defenses Against Format String Vulnerabilities • Stack defenses don't stop format string exploits – Canary value • ASLR and NX – Can make exploitation more difficult • Static code analysis tools – Generally find format string bugs • gcc – Warnings, but no format string defenses
- 17. Steps • Control a parameter • Find a target RAM location – That will control execution • Write 4 bytes to target RAM location • Insert shellcode • Find the shellcode in RAM • Write shellcode address to target RAM location
- 18. Control a Parameter • Insert four letters before the %x fields • Controls the fourth parameter – Note: sometimes it's much further down the list, such as parameter 300
- 19. Target RAM Options • Saved return address – Like the Buffer Overflows we did previously • Global Offset Table – Used to find shared library functions • Destructors table (DTORS) – Called when a program exits • C Library Hooks
- 20. Target RAM Options • "atexit" structure (link Ch 4n) • Any function pointer • In Windows, the default unhandled exception handler is easy to find and exploit
- 21. Disassemble in gdb • gdb -q fs • disassemble main • First it calls printf • With a format string vulnerability • Later it calls exit
- 22. Dynamic Relocation (also called Global Offset Table (GOT))
- 23. Targeting the GOT • Global Offset Table • Pointer to exit at 0804a014 • Change pointer to hijack execution
- 24. Writing to the GOT • gdb -q fs • info file -- see got.plt • b * main+76 -- after printf • x/1x 0x0804a014 • run $'x14xa0x04x08%x%x%x%n' • x/1x 0x0804a014
- 25. Python Code to Write 1 Word
- 26. Write 4 Bytes, All The Same
- 27. Write 4 Bytes, Increment=8
- 28. Write 4 Bytes, Increment=16
- 29. Write 00000000
- 30. Write Chosen Values in 4 Bytes
- 31. Write Chosen Values in 4 Bytes
- 32. Inserting Dummy Shellcode • xcc is BRK
- 33. View the Stack in gdb • Choose an address in the NOP sled
- 34. Dummy Exploit Runs to xcc
- 35. Testing for Bad Characters • x09 is bad
- 36. Testing for Bad Characters • 10 is bad
- 37. Testing for Bad Characters • Started at 11 = 0x0b • x20 is bad
- 38. Testing for Bad Characters • Started at 33 = 0x21 • No more bad characters
- 39. Generate Shellcode • msfvenom -p linux/x86/shell_bind_tcp • -b 'x00x09x0ax20' • PrependFork=true • -f python
- 40. Keep Total Length of Injection Constant • Required to keep the stack frame size constant
- 41. Final Check • Address in NOP sled • Shellcode intact
- 42. Shell (in gdb)
- 43. Outside gdb • Crashed with segfault on Kali 2018.1 • Had to add 0x30 to address