Official discussion thread for Restaurant. Please do not post any spoilers or big hints.
So...I've been on this one for a handful of hours and I'm getting the feeling I've misunderstood its "Easy" rating.
Is there a useful correlation between what the community rates and what I should expect to use in my own toolsets?
I ask because I've been writing my own codes against the binaries; at first just to see if I could get the flag out of the binaries themselves, but now I'm looking at whether the host server is involved (so I'm worrying about what might be randomized).
Am I making this too complicated, just about right or...?
Same consideration for me. I've decompiled the executable and I have seen the vulnerability, but I don't know how capture the flag. Send a rev shellcode on the server maybe?
That's what I was thinking, but knowing how compilers protect against certain mistakes (where the process suicides if testers go after them), I felt like I had left Easy...at least without using a tool. I guess I'll try anyway / try not to trip any protections.
Did anyone manage this challenge? I need in a small hint.
Hum... not that easy Is the goal is to inject a shellcode so access the server fs? I guess... I didn't find that much useful information in the code itself and it looks some protections were applied. Is it a ROP challenge?
Could someone who has solved this challenge PM me? I need a nudge.
I was able to exploit this on my local machine. However, seems like l*bc address on the remote machine is different. Can you please give me a hint on how to discover the remote l*bc address?
Just did this challenge. I would only call this challenge easy, in the sense that it is fairly straightforward IF you already know the techniques to defeat the protections on the binary (unless there's some glaring vuln that I missed ). In my mind, the challenge is not "total beginner easy".
DM me what you've tried and I'll be happy to provide nudges.
Click here to create an account.