pwnable.kr: crypto1 challenge
In the pwnable.kr challenge
crypto1 in the rookies section, we are given the following two files
Furthermore, there is a running instance of
pwnable.kr on port
9006. Our goal is to connect to this service and retrieve the flag.
We can infer from the two files the following facts:
- The only user-controlled inputs are the username and password strings.
- AES-128 (default) is used in CBC mode to encrypt the string
- Before the plain text is processed by AES, it is padded with NULL values (
\x00) 4. The function request_auth() will show us for every supplied username and password the corresponding cipher text.
- The password of a user is solely the SHA256 sum of the string
"username"+"cookie"(+ denotes concatenation here). Thus, the password of a user is entirely dependent only on his username and the cookie value.
- The initialization vector is constant.
- We are given credentials for the user guest:
guest / 8b465d23cb778d3636bf6c4c5e30d031675fd95cec7afea497d36146783fd3a1
- The flag will be read by client.py if and only if the return value retrieved from
server.pyis neither 0 or 1.
- The return value retrieved from server.py will only return a value different from 0 and 1 when the username is admin and the correct password is supplied for this user.
- As we know from (5), the password of admin can be computed once the secret cookie value is known.
- The username and password can only consist of values of the following character set:
So there are numerous ways of approaching this challenge and it is definitely helpful to have a good understanding of common cryptographic engineering problems and pitfalls.
I initially thought about whether it would be possible to somehow infer information about the cookie from the provided credentials of the user
However, the key to the challenge is to utilize the cipher text oracle and perform a chosen-plaintext attack. Hence, we have to understand which parts of the input change the corresponding parts of the output.
AES is a block cipher and operates on a block size of 16 bytes. Thus it is advisable to divide the cipher text into chunks of this size and choose different input parameters. Furthermore, we have to recall how our input is transformed BEFORE it is supplied as a plain text to the encryption routine.
The username is the first content of the plain text, followed by a single
"-", the password, another
"-" character and lastly the cookie.
When we choose for the username an input having at least 16 bytes, we note that the first 16 bytes of cipher text entirely depend on the username. For example, a username beginning with 16
"a" characters, i.e.
"aaaaaaaaaaaaaaaa", will always cause the first block of cipher text to be equal to
"166827d3124ce5db2b36e803b9115a49", irrespective of the other characters of the username or the password.
When we choose exactly 15 times the character
"a" as the username, we know that the first 16 bytes of the actual plain text will be
"aaaaaaaaaaaaaaa-", since the encryption routine will append a trailing
"-" as a delimiter between the username and password.
Similarly, when we choose exactly 14 times the character
"a" and an empty password, we know that the first 16 bytes of the actual plain text fed into AES will be
"aaaaaaaaaaaaaa--". This is due to the fact that the password is empty and an additional
"-" will be appended by the function
request_auth as a delimiter between the password and the cookie.
Now we arrive at the point where the actual magic happens. What if we choose exactly 13 times the character
"a" as the username and an empty password? As you correctly guessed, the function
request_auth will append two
"-" characters. Furthermore, it will append the first byte of the secret cookie value!
Yet, as we only can see the cipher text, we do not know immediately the corresponding plain text. But we can save the 16 bytes of cipher text as a reference block and compute cipher text blocks for all possible values of the first cookie byte. As soon as the computed cipher text block is equal to the reference block, we know we have correctly guessed the cookie byte value! This whole procedure is also known as one-byte-at-a-time decryption.
The details of the actual attack are a little bit more intricate, since we cannot directly compute cipher texts but have to rely on the
request_auth function, which will append
Concerning the guessing of the first cookie byte value, for the reference block we have to choose 13 times the character “-”. For the subsequent guesses, we will have to choose a username consisting of 15 times the character
"-" and the 16th character will be the guessed cookie byte value.
You are highly encouraged to work out a fully working decryption routine yourself. Once you have completed it, try a variant of the attack by keeping the username value constant and alter instead the password value.
For the sake of completeness, here you have my proposed solution: