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

API Rest BURP PRO

JULIO | Last updated: Feb 10, 2022 09:03PM UTC

We are automating the scan of launch URLs from the API point and we noticed the following behavior. 1 - launch scan API curl -vgw "\n" -X POST 'http://XXX.xxx.xxx.xx:91/APIKEY/v0.1/scan' -d '{"urls":[]}' So far everything is ok, we received the ID in the response to follow the progress of the scan; 2 - Get Scan Status curl -vgw "\n" -X GET 'http://xxx.xxx.xx.xxx:91/APIKEY/v0.1/scan/3' So far everything is ok: body { "task_id": "3", "scan_status": "crawling", "scan_metrics": { "crawl_requests_made": 16, "crawl_network_errors": 0, "crawl_unique_locations_visited": 8, "crawl_requests_queued": 0, "audit_queue_items_completed": 0, "audit_queue_items_waiting": 0, "audit_requests_made": 0, "audit_network_errors": 0, "issue_events": 0, "crawl_and_audit_caption": "Unauthenticated crawl. Estimating time remaining...", "crawl_and_audit_progress": -1 } Here's the problem: After restarting BURP and trying to resume checking the scan status, we get a 400 BAD Request message, not being able to follow any scan started before restarting the application. Status 400 Bad Request headers cache-control: no-cache, no-store, must-revalidate content-encoding: gzip content-length: 66 content-security-policy: default-src 'self'; script-src 'self'; img-src 'self'; style-src 'self'; frame-src 'self'; connect-src 'self' ws://localhost:3333; font-src 'self'; media-src 'self'; object-src 'none'; child-src 'self' blob: content-type: application/json; charset=utf-8 expires: 0 keep-alive: timeout=15 pragma: no-cache x-burp-version: 2020.9.2-4265 x-content-type-options: nosniff x-frame-options: DENY x-xss-protection: 1; mode=block body { "type": "ClientError", "error": "Task ID not found" }

Michelle, PortSwigger Agent | Last updated: Feb 11, 2022 09:47AM UTC

Thanks for getting in touch and reporting this issue. We have raised this with our developers, we don't have any timescales as yet but we have linked this thread so we can post back here when there are any updates.

Mitchell | Last updated: Dec 02, 2022 05:36PM UTC

Did this issue get resolved? I think I'm encountering the same problem

Ben, PortSwigger Agent | Last updated: Dec 06, 2022 12:20PM UTC