Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

v2.0.x Extender API iScanQueueItem.getPercentageComplete() does not work

Luca | Last updated: Nov 16, 2018 10:16PM UTC

While testing https://github.com/vmware/burp-rest-api/, we realized that there is a bug in the Burp Extender API iScanQueueItem.getPercentageComplete() for Burp Professional v2.x (beta). We have verified the problem with both 2.0.11 and 2.0.12. getPercentageComplete() always returns 0 - instead of the correct percentage. Please see https://github.com/vmware/burp-rest-api/issues/80 for the original bug.

Liam, PortSwigger Agent | Last updated: Nov 19, 2018 09:46AM UTC

Luca, we removed this functionality as it is no longer used by the Burp UI. We're likely to deprecate the feature unless you have a specific use case that requires it?

Burp User | Last updated: Nov 22, 2018 10:05AM UTC

The use case for me is the ability to have a REST API that is independent from the internal (currently limited) API exposed by Burp - see https://github.com/vmware/burp-rest-api I would expect the Extender APIs of Burp Suite v2 to be at least compatible with previous versions. This is probably breaking other extensions too.

Liam, PortSwigger Agent | Last updated: Nov 22, 2018 03:48PM UTC

Luca, we appreciate your point. We're just curious as to whether you have a specific use case that we could help facilitate? The new API does provide metrics of the whole scan.

Burp User | Last updated: Nov 23, 2018 10:40AM UTC

Is there a Javadoc of the new Extender API somewhere online? The use case is the ability to check the scan status using our custom Rest API

Liam, PortSwigger Agent | Last updated: Nov 23, 2018 10:46AM UTC

You can browse the API documentation at [Service URL]/[API key]. - https://portswigger.net/blog/burps-new-rest-api

Burp User | Last updated: Dec 13, 2018 11:20AM UTC

I am talking about the ***Extender API*** https://portswigger.net/burp/extender/api/index.html Is there a Javadoc of the new Extender API since it's not 100% compatible with previous versions?

PortSwigger Agent | Last updated: Dec 13, 2018 11:21AM UTC

We've tried to keep the API compatible and there are no new documents. If you notice anything that is not compatible, let us know. The only change I can think of is that sendToSpider results in callbacks to processHttpMessage with tool set to TOOL_SCANNER instead of TOOL_SPIDER. This is due to Spider being replaces by the new crawler and unfortunately breaks Headless Burp.

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