This is the first time I had to deal with this error in Burp and I was trying to figure out what was the problem. It seems there is a problem with Java which causes Burp to fail when accessing some specific websites. This is the screen you get when this particular error occurs.
Figure 1 - Burp Error handshake alert: unrecognized_name
If you ever stumble upon this problem the solution is easy once you know what to do. As a start, make sure you have the latest version of Java installed.
After posting this on Twitter, Burp Suite (@Burp_Suite) responded with the following tweet. Well done Burp Suite!
Figure 2 - Burp Suite response to the issue
Technically, one of the ways to solve the problem is by going to the Options tab in Burp, scroll down to SSL Negotiation Workarounds and tick the box "Allow unsafe renegotiation (required for some client certificates)".
On the other hand, I tend to use a .bat file for running Burp. This allows me to be flexible when I want to specify any additional parameters and in this case it came handy.
My .bat file looks like this:
@echo off
java -jar C:\burpsuite\burpsuite_free_v1.6.01.jar
In order to fix the error, either user a .bat file like I have or start Burp with the following command Java command:
@echo off
java -Djsse.enableSNIExtension=False -jar C:\burpsuite\burpsuite_free_v1.6.01.jar
This should address the problem and Burp will start working as it should. On a side note, if Firefox is the browser you prefer to use with Burp, you will notice that after the latest update there is a problem with the certificates. To solve this problem you will have to visit the page http://Burp while you are connected to the Burp proxy. Burp will respond with the following page:
Figure 3 - Downloading the Burp CA Certificate
Click the CA Certificate link, and save the Burp Certificate on your system. Then go to Firefox > Options and select Advanced.
Figure 4 - Importing the Burp CA Certification into Firefox
Click on View Certificates and import your Burp Certificate. Refresh your Firefox page and any certificate issue should go away.
No comments:
Post a Comment