A7: 2021 | JWT Tokens (13) | Cycubix Docs
Refreshing a token
It is important to implement a good strategy for refreshing an access token. This assignment is based on a vulnerability found in a private bug bounty program on Bugcrowd, you can read the full write up here
Assignment
From a breach of last year the following logfile is available here Can you find a way to order the books but let Tom pay for them?
Solution
Hints: Look at the access log you will find a token there. The token from the access log is no longer valid, can you find a way to refresh it?. The endpoint for refreshing a token is 'JWT/refresh/newToken'. Use the found access token in the Authorization: Bearer header and use your own refresh token.
Intercept the post request with ZAP after you hit the chekout request.
Send the request to the request editor. See Jerry's past credentials.
Open the logfile to find the session information.
Check the checkout token:
Other way to find the token is by intercepting the POST request with ZAP.
Also, you can see that the response says user is Jerry not Tom.
Insert the checkout token into https://jwt.io/.
We will need to change the header and payload to validate a new token. So we will need to ask for an access token renewal using “Tom” access token present in the given log and “Jerry” refresh token obtained by loading the lesson page.
Copy the header and open the decoder in Zap from the tools tab. Paste the header and decode it into base64. Then change it into "alg:none" and encode it again into base 64.
Paste the result into the header of the token in JWT and check that effectively the header refers to alg=none.
Now go ahead and paste the claims in the payload into the decoder in Zap. Decode it into base64. Then copy that value, change the values into "Tom" and "True" and encode it in base64.
Once you have your header and payload paste it in the POST request in ZAP. Leave the signature blank.
Below you can see the changed token.
Check the response:
Last updated
