Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Auditing stops due to token expiring

Warren | Last updated: May 13, 2020 02:13PM UTC

Website assigns a token once a client logs in. During the auditing stage this token is expiring and the audit fails. Example of issues log: Info Task 3 Paused due to error: 12 consecutive audit items have failed. Debug Task 3 [6] Skipping phase A1 for /cgx/mystore-users/profile Debug Task 3 Skipping phase A1 for /cgx/theme/base/thirdparty/html5shiv/ Info Task 3 Paused due to error: 11 consecutive audit items have failed. Info Task 3 Paused due to error: 10 consecutive audit items have failed. Debug Task 3 Skipping phase A1 for /cgx/mystore-users/logout Is there a way to force the scan to use a token?

Ben, PortSwigger Agent | Last updated: May 14, 2020 10:43AM UTC

Hi Warren, Are you looking to use a specific token during the scan (rather than the one assigned at login)? You could look to take advantage of Burp's Session Handling Rule, as detailed on the following page: https://portswigger.net/burp/documentation/desktop/options/sessions/rule-editor

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