Natas 3 -> 4

user: natas3
pass: sJIJNW6ucpu6HPZ1ZAchaDtwd7oGrD14

This looks familiar... Let's see what we've got here. Oh, but wait - there's a comment in the HTML. It says that not even Google will find it this time. How do websites control what Google does with them?


The /robots.txt page says:

User-agent: *
Disallow: /s3cr3t/

So, what do we do? Why, let's go to the /s3cr3t page, of course! There we find another users.txt file, and our password for the next challenge.































Comments











Post a Comment























Popular posts from this blog









Natas 7 -> 8





















user: natas7  pass: 7z3hEENjQtflzgnT29q7wAvMNfZdh0i9   Ooh, links! But neither one seems terribly helpful. As should be your first instinct by this point, let's look at the developer tools. There's a hlepful comment in there.   "hint: password for webuser natas8 is in /etc/natas_webpass/natas8"   Well, that seems straightforward. However, http://natas7.natas.labs.overthewire.org/etc/natas_webpass/natas8 doesn't exist. So what are we missing?   Closer examination of the links on the home page show us that there's a /index.php bit of each URL that might be important. So let's try it.   http://natas7.natas.labs.overthewire.org/index.php?page=/etc/natas_webpass/natas8 should get you what you're looking for.








Read more










Natas 11 -> 12





















user: natas11  pass: U82q5TCMMQ9xuFoI3dYX61s7OZD9JKoK   OK, this level is a bit tricky. We start out looking at the source code, and we are faced with several functions. xor_encrypt seems to encrypt any text sent to it by xoring the input character by character with the key we want.   loadData checks to see if the cookie sent with the data matches the background color, and has the 'showpassword' field in it. If the background color sent with the data and sent in the cookie match,  it stores the color and the showpassword boolean - this is probably the key to getting the key.   The big trick here is that there's an XOR encryption going on. At first this might seem tricky, but on closer consideration we remember that if   xor myword => cypher, then  xor cypher => myword.   in the function saveData, we wee that the cookie for the website is set with base64-encode, xor_encrypt, and json-encode. Therefore, we start with the cookie. We know we want to base64-decode, so let&








Read more










Natas 8 -> 9





















user: natas8  pass: DBfUBfqQG69KvJvJ1iAbMoIpwSNQ9bWe   Another secret, but this time the source code shows that the secret has been encoded. The language we're seeing here in the midst of the HTML is PHP. So, let's go to our closest friendly PHP station: the terminal. Running   >>>php -a   will get you into interactive mode in the terminal. Now it's just a matter of reversing the encryption on the secret. We know that the encoded one is  "3d3d516343746d4d6d6c315669563362" , and that to get it there we ran   return bin2hex(strrev(base64_encode($secret)));   Therefore, we try the opposite:   print base64_decode( strrev(hex2 bin( $encoded)));   This yields the secret we were looking for, which when inputted gives us our password.








Read more