The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Intruder Post Processor Extension

Wyatt | Last updated: Sep 20, 2023 07:28PM UTC

Hi PortSwigger Team, I use Intruder for a lot of heavy web fuzzing and would like to suggest a post-processor script/extension capability. With generic fuzzing, table views like Intruder and FFUF provide an opportunity for users to look for interesting differences. Burp offers the ability to sort columns, which helps a lot to find outliers. Turbo Intruder provides the `handleResponse` function to create some logic in how the response is processed. Users can modify this function to only add interesting responses, which can help filter out uninteresting results. It would be a nice addition to Burp to allow users to add a post-processor to the standard Intruder service to take advantage of all of the various attack settings. With Turbo Intruder, users have to re-write the logic for each attack. Similar to other items in Intruder, I think the PortSwigger team could have some default options, such as: Only display 200 status codes, remove 429 status codes, response times greater than X seconds, etc. An extension would provide the most flexibility for Burp users. They could take advantage of the Montoya API to define complex logic based off request/response pairs. Perhaps there could be different ways to process results. The standard could be that each response is processed as it is received, but another example could be each Intruder payload set being processed as a collection to identify outliers. This feature would save me countless hours of sifting through uninteresting results. It should help save on RAM as well since the results table can be filtered down to a smaller size.

Michelle, PortSwigger Agent | Last updated: Sep 21, 2023 12:17PM UTC