Time for a stego writeup..
Can you hear it? Sounds like a flag… Note: The flag only contains lowercase characters.
The Plague has tried to make things easy for you in this service, but not too easy. He’s called The Plague, not The Nice Guy. The service should be running at 22.214.171.124:9999.
Tenement is a remote pwnable – it’s a normal x86 binary.
Upon initialization it loads a json file, using libjansson, which contains the flag and an array with memory addresses. The flow goes like this:
The Plague has purchased the newest invention, Polygon Shifter to protect his website. This cutting edge technology is made available by Polygon Security, and they have a demo page on their website. They claim bots can no longer attack the website protected by the Polygon Shifter. Do we need to manually bruteforce the credentials?
On the Polygonshift website is a live demo form where you can login as user test/test or as user admin/?????. After logging in as user admin with password: a’ OR 1=1 and username=’admin’# we get the message
Hello, admin!! My password is the flag!. So, we have a blind SQLi and the goal is to get the password of the admin user.
Kappa is a network service that is a very basic text-based pokemon game. In the end we found multiple bugs in the service, but the one we used was so cleanly exploitable that we think this was probably the intended solution.
When you connect, you get this menu:
We found this server with two open ports. Can you find out what these ports do and login to the server? It is advisable to use a seperate VM for this challenge.
Nmap scan report (126.96.36.199)
Host is up (0.026s latency).
PORT STATE SERVICE
22/tcp open ssh
8140/tcp open unknown
This challenge was ment to be an easy multi stage challenge, but was apparently a lot harder than intended, cause it only had 7 solves. The challenge contains three levels which require shell access. Since we didn’t want to have hundreds of logins on the system, we created an extra step to get access to the system.
We found this strange website. (http://188.8.131.52/)
For this challenge we only get a website with a sum on it.
112 + 386 + 712 + 1398 + 8771 + 11982 + 15397 + 23984 = 51037
This doesn’t give us much information. How about we look at the headers.
OMG, Eindbazen got hacked. Can you figure out what this evil hacker did?
This was an easy challenge, and pretty straight forward what to do. It was meant to be solved by a lot of teams, and they did, 145 teams managed to solve it. There are a lot of write-ups for this challenge, so I will explain in short what was the intended solution.
We designed a new login procedure for our Online Tulip Shop. Can you test if it is hacker proof?
The WEB100 challenge was apparently harder than expected with only 10 solves. The goal of this challenge was to grep the admin password from the sqlite database with a SQL injection. The SQL injection however was not in one of the normal places, but in the key name of the password field.
We found some crypto ciphers on our attic. Can you decipher all text and put together the flag?
This challenge was meant to be a simple task, but which required a lot of work. It gave you six encrypted messages which you need to decrypt to get parts of the key .