CLICK HERE FOR BLOGGER TEMPLATES AND MYSPACE LAYOUTS »

Saturday, August 22, 2020

NcN 2015 CTF - theAnswer Writeup


1. Overview

Is an elf32 static and stripped binary, but the good news is that it was compiled with gcc and it will not have shitty runtimes and libs to fingerprint, just the libc ... and libprhrhead
This binary is writed by Ricardo J Rodrigez

When it's executed, it seems that is computing the flag:


But this process never ends .... let's see what strace say:


There is a thread deadlock, maybe the start point can be looking in IDA the xrefs of 0x403a85
Maybe we can think about an encrypted flag that is not decrypting because of the lock.

This can be solved in two ways:

  • static: understanding the cryptosystem and programming our own decryptor
  • dynamic: fixing the the binary and running it (hard: antidebug, futex, rands ...)


At first sight I thought that dynamic approach were quicker, but it turned more complex than the static approach.


2. Static approach

Crawling the xrefs to the futex, it is possible to locate the main:



With libc/libpthread function fingerprinting or a bit of manual work, we have the symbols, here is the main, where 255 threads are created and joined, when the threads end, the xor key is calculated and it calls the print_flag:



The code of the thread is passed to the libc_pthread_create, IDA recognize this area as data but can be selected as code and function.

This is the thread code decompiled, where we can observe two infinite loops for ptrace detection and preload (although is static) this antidebug/antihook are easy to detect at this point.


we have to observe the important thing, is the key random?? well, with the same seed the random sequence will be the same, then the key is "hidden" in the predictability of the random.

If the threads are not executed on the creation order, the key will be wrong because is xored with the th_id which is the identify of current thread.

The print_key function, do the xor between the key and the flag_cyphertext byte by byte.


And here we have the seed and the first bytes of the cypher-text:



With radare we can convert this to a c variable quickly:


And here is the flag cyphertext:


And with some radare magics, we have the c initialized array:


radare, is full featured :)

With a bit of rand() calibration here is the solution ...



The code:
https://github.com/NocONName/CTF_NcN2k15/blob/master/theAnswer/solution.c





3. The Dynamic Approach

First we have to patch the anti-debugs, on beginning of the thread there is two evident anti-debugs (well anti preload hook and anti ptrace debugging) the infinite loop also makes the anti-debug more evident:



There are also a third anti-debug, a bit more silent, if detects a debugger trough the first available descriptor, and here comes the fucking part, don't crash the execution, the execution continues but the seed is modified a bit, then the decryption key will not be ok.





Ok, the seed is incremented by one, this could be a normal program feature, but this is only triggered if the fileno(open("/","r")) > 3 this is a well known anti-debug, that also can be seen from a traced execution.

Ok, just one byte patch,  seed+=1  to  seed+=0,   (add eax, 1   to add eax, 0)

before:


after:



To patch the two infinite loops, just nop the two bytes of each jmp $-0



Ok, but repairing this binary is harder than building a decryptor, we need to fix more things:

  •  The sleep(randInt(1,3)) of the beginning of the thread to execute the threads in the correct order
  •  Modify the pthread_cond_wait to avoid the futex()
  • We also need to calibrate de rand() to get the key (just patch the sleep and add other rand() before the pthread_create loop
Adding the extra rand() can be done with a patch because from gdb is not possible to make a call rand() in this binary.

With this modifications, the binary will print the key by itself. 

More articles


  1. Hacking Tools For Pc
  2. Hack Tools For Ubuntu
  3. New Hack Tools
  4. Tools 4 Hack
  5. Blackhat Hacker Tools
  6. Hacker Tools Free
  7. Pentest Tools List
  8. Hack Tools Github
  9. Hack Tools For Windows
  10. Hacking Tools Windows
  11. Pentest Tools Find Subdomains
  12. Easy Hack Tools
  13. Hack Tools For Pc
  14. Hacker Tools 2020
  15. Pentest Tools Linux
  16. Hack Tools For Pc
  17. Hacker Tools Apk
  18. Android Hack Tools Github
  19. Pentest Tools For Ubuntu
  20. Hacking Tools For Beginners
  21. Hack Tools
  22. Hacking Tools For Beginners
  23. How To Make Hacking Tools
  24. Hackers Toolbox
  25. Easy Hack Tools
  26. Hacker Tools For Mac
  27. Hacking Tools For Games
  28. Hacking Tools
  29. Hacker Tools For Pc
  30. Pentest Tools Find Subdomains
  31. Pentest Tools Url Fuzzer
  32. Pentest Tools Subdomain
  33. Hacking Tools Windows 10
  34. Hacking Apps
  35. Computer Hacker
  36. Beginner Hacker Tools
  37. Pentest Tools List
  38. Beginner Hacker Tools
  39. Tools 4 Hack
  40. Hack Tools For Games
  41. Pentest Tools Windows
  42. Pentest Tools Find Subdomains
  43. Hack App
  44. Wifi Hacker Tools For Windows
  45. Hacker Tools For Windows
  46. Growth Hacker Tools
  47. Hacker Tools Software
  48. Hacking Tools For Windows
  49. Hacker Tools Free Download
  50. Hacking Tools Github
  51. Hack Tools Pc
  52. Hacking Tools For Windows Free Download
  53. Hacker Search Tools
  54. Hack Tools For Games
  55. Pentest Tools For Windows
  56. What Are Hacking Tools
  57. Hacker Tools 2019
  58. Hack And Tools
  59. Hacker Tool Kit

0 comments: