CSAW CTF 2015 - Throwback
- We can see a recent bugfix to CTFd, preventing unauthed admin calls at https://github.com/CTFd/CTFd/commit/9578355143d7af675fc4776b0f2de802be91e261.
CSAW CTF 2015 - K_{Stairs}
The site has a maze game that you must navigate through. On the /play tab, it shows a login screen, so an account is needed to play. Registering for an account, it automatically logs you in. The hint is that you need a compass to iwn, which is 10 tokens. The first account made will have none. However, with each account created, three more tokens are added to the current account compared to your previous account, due to cookies. If someone else tries to login with your credentials, they will not have the same amount of tokens.
CSAW CTF 2015 - Alexander Taylor
The first part of the challenge is to find the initals of the club Alex was in university. Googling “Alexander Taylor Raytheon” brings up his LinkedIn, which shows that he went to the University of South Florida and was president of the Whitehatters Computer Security Club. Using the format:
http://fuzyll.com/csaw2015/<initials here>
http://fuzyll.com/csaw2015/wcsc is the first part. It says:
CSAW CTF 2015 - airport
Unzipping the airport file, there are two folders. __MACOSX is automatically generated by OSX and it is irrelevant to the challenge. steghide.jpg is compatible with the steghide tool. Identifying the four airports as:
1st: Jose Marti, Cuba
2nd: HongKong, China
3rd: LAX, USA
4th: Toranto Pearson, Canada
The third was difficult to guess because it was in Korean, but there were not many airports in Korea to guess from. However, the blog was speaking of the LAX airport.
The fourth was difficult to guess because a reverse image search could not find a result, unlike the other three. Using the highway numbers listed, the airport was found on Google Maps.
Enter in the airport codes in consecutive order.
steghide extract -p "HAVHKGLAXYYZ" -sf steghide.jpg
CSAW CTF 2014 VM
A few weeks ago the CSAW CTF was run from NYU-Poly and over 2500 teams registered to play.
Build It Break Fix It
These past few weeks, we participated in Build it Break it Fix it. Our team consisted of Ancat, Blankwall, ColdHeat and Kiwi. Contestants were tasked with writing correct, secure and fast code in the Build it round. Next, the Break it round has them looking for bugs and vulnerabilities in other teams’ submissions. Finally, the Fix it round allows teams to unify bugs submissions against their team and gain back points.