CustomDeserializer

This extension speeds up manual testing of web applications by performing custom deserialization. Adds a custom editor tab for decoding/encoding parameters on the fly and integrates with Burp Suite Scanner and Intruder for automation.

Full description, set up guide, examples and demo: https://github.com/marcotinari/CustomDeserializer

Quick Set up guide - editor tab

1. Click on the Deserializer tab
2. Enter the name of the parameter You want to deal with
3. Set the parameter position: POST for body, GET for URL and COOKIE for Cookie header
4. Select the transformation function to be applied.
   • When selected, the functions will be applied as follows
   • deserialized data -> ASCII2HEX() -> Base64decode() -> URLdecode() -> serialized data
   • Serialized data -> URLdecode() -> Base64decode() -> ASCII2HEX() -> deserialized data
5. Click on the small Apply button

Click here for a screenshot of the Deserializer tab

Quick set up guide - Intruder integration

1. enable the Intruder integration in the Deserializer tab
2. send the Request to the Intruder tab
3. replace the encoded parameter value with the decoded value
4. define the Intruder insertion points with placeholder
5. start the Intruder attack
6. the parameter values will be automatically encoded according to the selected transformation functions
7. TIP: In the Intruder attack result/history You will find the decoded version of the payload. Use an external Extension (e.g. Logger++ is a great extension from Soroush Dalili, NCC Group) if You want to check the actual HTTP Request after being transformed by the extension

Quick Set up guide - Scanner integration

1. enable the Intruder integration in the Deserializer tab
2. send the Request to the Intruder tab
3. replace the encoded parameter value with the decoded value (check Intruder integration instruction for examples)
4. set the insertion points with the placeholders
5. right click -> Actively scan defined insertion point
6. while scanning, the parameter values will be automatically ancoded according to the selected transformation functions
7. TIP: In the Scanner finding issues HTTP Requests You will find the decoded version of the payload used. Use an external Extension (e.g. Logger++ is a great extension from Soroush Dalili, NCC Group) if You want to check the actual HTTP Request after being transformed by the extension

Extension demo How-To

Using the extension demo