Burp Suite User Forum

Create new post

Macro define custom parameter location in response not working

Marc | Last updated: Jul 22, 2016 08:27AM UTC

Hi, We are using Burp Pro 1.7.03 and when trying to "Define a Custom Parameter" in the "Configure Macro Item" we can't get Burp to get anything; when we test the macro no "Derived parameters" or "Failed parameters" are shown. We tried the "Define start and end" and the "Extract from regex group" approach with no luck. Besides the "Test Macro" result we tried to use the macro with the Intruder, creating a corresponding "Session Handling Rule" to run the macro before each request. We can see how the session handling rule applies ok, but the parameter that the macro should extract from the response is not updated in the in the request made by the Intruder. Even thought we think it's not related, we tried to activate and de-activate the Cookie handling options ("Add cookies received..." & "Use cookies from the session...") and the "Extracted value is URL-encoded" options, but with the same result. It simply looks like if the feature was broken: are we missing something?

PortSwigger Agent | Last updated: Jul 22, 2016 08:39AM UTC

This feature is working as expected in our testing. When you defined a custom parameter location in the response, did you give the custom parameter the same name as the consequential request parameter that you want to update? Burp uses the parameter name to decide which request parameters to update.

Burp User | Last updated: Apr 07, 2019 07:31PM UTC

I am also experiencing this situation, where i am not able to reflect the custom parameter location in response in a subsequent request parameter. I gave correct name and all but not sure it is not working.

PortSwigger Agent | Last updated: Apr 08, 2019 10:03AM UTC

Karun - sorry to hear you're having difficulty. Using a custom parameter location works correctly for me. You may be able to self-diagnose this using Session Tracer. If you're still having difficulty, could you save your project options and send them to support@portswigger.net, with some screenshots from Session Tracer showing the problem.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.