Next challenge I’ll be writing for is Natas. Extremely fun challenge although sometimes frustrating if you’re not sure what you’re trying to do. First few challenges are easy, so I’ll be doing a few per post.

Natas 0

It says it’s on the page, yet we don’t see it, do we? Right click anywhere on
the page and view the source. You’ll notice a comment:

<!--The password for natas1 is gtVrDuiDfck831PqWsLEZy5gyDz1clto -->

Natas 1

Eh, more of the same, you got different ways to do this though:

  • Disable JavaScript (mayeb use NoScript).
  • Use a proxy (Fiddler or Burp suite).
  • Right click outside of the white block.
<!--The password for natas2 is ZluruAthQk7Q2MqmDeTiUij2ZvWy2mBi -->

Natas 2

There’s nothing on this page, hmm. Let’s check the source again, shall we?

Nothing special about it that <img> tag (although would’ve been cool if the password was in the image comment) but it’s under http://natas2.natas/


Open users.txt, you’ll find the password to the next level.

# username:password

Natas 3

Let’s check the source again.

<!-- No more information leaks!! Not even Google will find it this time... -->

Sneaky, maybe we should play a little with Google operators /Google dorks?


A hidden directory! Again, you’ll find your password under users.txt.


Natas 4

It looks like it’s asking about the referrerfield in the HTTP response. It has many applications like tracking source in advertisement, or security related like verifying the user is redirected from the expected page, particularly useful against XSS and session hijacking.

Using Fiddler

First, let’s capture the request we want to manipulate:


Drag the request from the log to “Composer” tab. You’ll get the chance to edit the request before submitting it. Add Referer: then click “Execute”.

Go back to the “Inspector” tab and below the request you’ll find the response body, decode it if needed and you’ll find the password.


Access granted. The password for natas5 is iX6IOfmpN7AYOQGPwtn3fXpbaJVJcHfq.

Natas 5

You're not logged in

Well, let’s trick the server into believing we’re logged in. Let’s see what Fiddler reveals in the server response body.

HTTP/1.1 200 OK
Date: Thu, 27 Oct 2016 21:18:31 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Powered-By: PHP/5.5.9-1ubuntu4.20
Set-Cookie: **loggedin=0**
Vary: Accept-Encoding
Content-Length: 855
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html

What if we set loggedin to 1? Fire up the console in your browser and type document.cookie="loggedin=1"?

Refresh the page, you got your password!

Access granted. The password for natas6 is aGoY4q2Dc6MgDq4oL4YtoKtyAg9PeHa1