Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Help Alerts java.net.SocketException: Connection reset

Adam | Last updated: Dec 22, 2016 05:29PM UTC

When I am actively scanning our website on the internal IP address with Burp Suite Pro, I get a lot of java.net.SocketException: Connection reset So here is the setup of the scan I set the IP address to hostname in the project options so when, I look at the proxy tab-->> http history tab shows internal ip address correctly then I open that website (http only) then I add it to the scope I spider the website then select Actively scan this branch, I do this for each branch Then I go to Scanner tab -->> Scan queue The fields that are available there I see errors then Alerts tab flashing I go look at the alert it is java one The scan will scan finish each area showing issues, requests, inserting points, etc... End of all the scanning I have many of them showing errors but I can not find those in a report or details. My idea for this issue might be the firewalls setup not allow all the vulnerabilities testing though?

PortSwigger Agent | Last updated: Dec 23, 2016 09:18AM UTC

It's hard to know what might be causing this problem, but if Burp is intermittently getting "Connection reset" errors when making non-SSL connections to a host, then this might suggest that the network connection is unreliable. If you send a request over and over using Repeater (or using Intruder with null payloads), do you sometimes see the same error?

Burp User | Last updated: Dec 28, 2016 02:00PM UTC

First Dafydd thank you for looking into this issue Sorry for the late reply I can see on the firewall resets but not as many as I see in burp suite alters I will try that to see what will happen. Thank you again for your help with this

PortSwigger Agent | Last updated: Dec 29, 2016 11:27AM UTC

Thanks for confirming. Let us know if you run into any other issues.

Burp User | Last updated: Jan 05, 2017 04:50PM UTC

Sorry for the late reply, I was not able to scan until today. After having a few setting change on the firewall for this test today. No more alerts, so the firewall was causing those resets

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