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

Install the required components for Browser Powered Scanning

Eric | Last updated: May 28, 2021 03:11PM UTC

I'm new to Burp Enterprise, and my credentialed scans are failing with an error that my hardware doesn't support Browser Powered scanning. After investigation, I have enough disk space, CPU, and RAM assigned. One support article mentioned checking file rights on the directory where the chrome sandbox is located. On my debian system, that directory does not exist under /home/burpsuite/.BurpSuite/.. This leads me to think that something was not installed (is missing). I cannot find instructions specific to how to install that component. So I am looking for any insight on what I could try as next steps to troubleshoot this further.

Liam, PortSwigger Agent | Last updated: Jun 02, 2021 10:49AM UTC

Hi Eric We think it's unlikely a disk space issue. Could you provide us with more details about your installation? Could you also provide the scan logs and agent logs? - https://portswigger.net/burp/documentation/enterprise/troubleshooting .BurpSuite will be placed in the data directory chosen when installing.

Eric | Last updated: Jul 14, 2021 07:04PM UTC

Good day, I thought I had resolved this, as this was related to s file rights issue, but it continues to fail again. so I am attempting to gather the logs, but the instructions provided in the troubleshooting link do not seem to match my interface. The instructions state to navigate to the SCAN DETAILS section of a failed scan and that the MORE ACTION menu will allow me to download the scan log and Burp Scanner's event log, however my interface does not have a MORE ACTION section. It there an updated troubleshooting document as perhaps the interface has evolved and changed. As a side note, the commands I executed to get it to run initially where: cd /var/lib/BurpSuiteEnterpriseEdition/burpbrowser/90.0.4430.212 sudo chown root:root chrome-sandbox sudo chmod 4755 chrome-sandbox

Liam, PortSwigger Agent | Last updated: Jul 15, 2021 08:45AM UTC

Hi Eric. Which version of Burp Suite Enterprise are you using?

Eric | Last updated: Jul 15, 2021 01:43PM UTC

ABOUT indicates: Version: 2021.6-7240, Java version: 11.0.10

Liam, PortSwigger Agent | Last updated: Jul 16, 2021 08:40AM UTC

These logs are now available in the Reporting and Logs tab of the scan view. We'll get this changed in the docs. You can email these to support@portswigger.net. Please let us know if you need any further assistance.

Eric | Last updated: Jul 16, 2021 03:05PM UTC

Please find the required log file at this link to troubleshoot the above issue. https://www.sugarsync.com/pf/D3157822_09567242_7467876

Liam, PortSwigger Agent | Last updated: Jul 19, 2021 12:27PM UTC

Hi Eric, thanks for the logs. 2021-07-13 23:15:21 [e] INFO - Exception report: 2021-07-13 23:15:21 [e] INFO - Category: RETHROWN 2021-07-13 23:15:21 [e] INFO - Detail: 2021-07-13 23:15:21 [e] INFO - burp.e4z: net.portswigger.devtools.client.a2: Refusing to start browser as your current configuration does not support running without sandbox Could you try disabling the sandbox with the following JSON config: { "project_options":{ "misc":{ "embedded_browser":{ "allow_running_without_sandbox":true } } } }

Eric | Last updated: Jul 21, 2021 01:27PM UTC

I found the issue. It seems that the Chrome Sandbox updated to a new version and the file rights are always wrong. I needed to redo the commands I did the first time to get things working (see commands below). Is there a fix documented for this so that the system doesn't stop working when the sandbox updates? (was on version 90.0.4430.212 and working, then version changed) cd /var/lib/BurpSuiteEnterpriseEdition/burpbrowser/91.0.4472.114 sudo chown root:root chrome-sandbox sudo chmod 4755 chrome-sandbox

Liam, PortSwigger Agent | Last updated: Jul 22, 2021 09:45AM UTC