Research Academy
My account Customers About Blog Careers Legal Contact Resellers
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

Tricky Issues for Different HTTP Methods in Burp-Suite Active Scan

Peter | Last updated: Dec 14, 2016 08:41AM UTC

Dear Experts, We get a very tricky issue that, when we're trying to do active scan for some HTTP requests [the requests are triggered by our extension program using the burp interfaces], the requests with method type "POST/PATCH" can continue with correct responses and find some security issues, while the requests with method type "GET/DELETE" won't get any responses and finally will be marked as "abandoned - too many errors". We tested these requests manually with some web tools such as Fiddler/PostMan, but we can get the correct results for all the requests, regardless of the HTTP method types... My questions: 1. Is there any special configuration that causes this issue? But unfortunately I cannot find any clues from the options in burp GUI. 2. What kind of scenario will be treated as "abandoned - too many errors" in Burp? Connection failure, status code or something else? My environment: Windows 8.1, Oracle JDK/1.8.0_112, Burp-Suite professional 1.7.13. This tricky issue is blocking us and we cannot find clues from the help document, wait your reply online and thanks very much! Regards, Peter

PortSwigger Agent | Last updated: Dec 14, 2016 09:15AM UTC

You will see the "Abandoned - too many errors" in two main situations: (a) Burp is repeatedly running into connection failures, timeouts, etc. at the network level for this item; (b) Burp encounters too many internal errors/exceptions while scanning the item, which may be the result of a bug within Burp. To investigate further, we would suggest: 1. Disable all extensions. 2. Install the Custom Logger extension from the BApp Store. 3. Run a scan against a single item that causes the problem. 4. Look at the requests that are made in the Custom Logger tab, to see where exactly the scan stops, to understand if there are network errors or if there is something else unusual about the request or response when the problem happens. 5. Email us your debug ID (at User options / Misc / Performance feedback) and we'll see if we have any relevant errors logged for your instance of Burp.

Burp User | Last updated: Dec 15, 2016 01:44AM UTC