Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Error when using carbonator

Prasuna | Last updated: Dec 18, 2018 08:51AM UTC

I get below error when using carbonator Initiating Carbonator Against: http://day191-181101-sql-274h.qa /rest/connect/ burp.ysg@1d01dc2f Sending new URL to Vulnerability Scanner: URL # 1 Sending new URL to Vulnerability Scanner: URL # 2 Sending new URL to Vulnerability Scanner: URL # 3 Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset New issue identified: Issue # 1 Scanner: java.net.SocketException: Connection reset Sending new URL to Vulnerability Scanner: URL # 4 Sending new URL to Vulnerability Scanner: URL # 5 Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset Scanner: java.net.SocketException: Connection reset New issue identified: Issue # 2 Suite: Failed to connect to the configured Collaborator server. New issue identified: Issue # 3 New issue identified: Issue # 4 No packets seen in the last 5 seconds. Removing Listeners Generating Report

PortSwigger Agent | Last updated: Dec 18, 2018 09:50AM UTC

It looks like you've got a slightly unreliable network connection, with a few connections being dropped. You should still be able to get usable results from this. If the results look reasonable and are consistent across multiple scans, I would just ignore these errors. You may be able to reduce the errors by reducing the number of concurrent requests in the Scanner configuration.

Burp User | Last updated: Dec 21, 2018 09:49AM UTC

Thank you for responding to this issue. The connections seem to be fine, I do not see any issue there. Not sure if the default collaborator server that is being used is correctly configured, because when I do a health check from project options-->misc-->burp collaborator server , I do get lot of warnings and I get "polling server connecttion " error as shown below: I am using burpsuite professional , which I think uses default collaborator. I restarted burp , but same issue exists. Health Check errors:- ======================= Initiating health check Server address resolution Success Server HTTP connection Warning Server HTTPS connection (trust enforced) Warning Server HTTPS connection (trust not enforced) Warning Server SMTP connection on port 25 Warning Server SMTP connection on port 587 Warning Server SMTPS connection (trust enforced) Warning Server SMTPS connection (trust not enforced) Warning Polling server address resolution Success Polling server connection Error No connections to etbobwq51hhe8l2kc48f3632vt16fpz73as.burpcollaborator.net could be opened. The collaborator may still work, as long as the server under test can connect to this port. No connections to the polling server at polling.burpcollaborator.net could be opened. The collaborator will not work in this configuration.

PortSwigger Agent | Last updated: Dec 21, 2018 09:56AM UTC

Hi Prasuna, Thanks for following up. Yes, that health check indicates that you can't access the public Collaborator. Are you on a corporate network? Perhaps you need to use an upstream proxy to access the Internet. Please let us know if you need any further assistance.

Burp User | Last updated: Jan 03, 2019 04:58AM UTC

Thank you Paul. Yes I am on corporate network. Not sure how to setup upstream proxy. Will try to figure that out.

PortSwigger Agent | Last updated: Jan 03, 2019 08:01AM UTC

Hi Prasuna, Thanks for following up. Please look in User options > Connections > Upstream Proxy Servers. You will need an IP address and port for the proxy server. You may be able to get this by looking at your browser configuration. Alternatively, ask your network administrator. Please let us know if you need any further assistance.

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