Insecure Desarialization
Last updated
Last updated
online debugger:
Try to change object ex. for administrator
Insecure deserialization of object - fn that delete file (unlink)
set access token to integer, and bypass authorization
O:4:"User":2:{s:8:"username";s:13:"administrator";s:12:"access_token";i:0;}
use functionality of the app to delete file
Edit the serialized data so that the avatar_link
points to /home/carlos/morale.txt
. Remember to update the length indicator. The modified attribute should look like this:
s:11:"avatar_link";s:23:"/home/carlos/morale.txt"
Click "Apply changes". The modified object will automatically be re-encoded and updated in the request.
Change the request line to POST /my-account/delete
and send the request. Your account will be deleted, along with Carlos's morale.txt
file.
replace session cookie inside browser
Consider a case where this loose comparison operator is used in conjunction with user-controllable data from a deserialized object. This could potentially result in dangerous .