Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Web server's SSL (HTTPS) does not agree with Firefox 62

ILGUIZ | Last updated: Sep 20, 2018 05:50PM UTC

Firefox 62 offers the following "cipher suites" TLS_AES_128_GCM_SHA256 (0x1301) TLS_CHACHA20_POLY1305_SHA256 (0x1303) TLS_AES_256_GCM_SHA384 (0x1302) TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca9) TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8) TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) and the BURPSuiteEnterprise's web server responds with a handshake failure, Alert Message Level: Fatal (2) Description: Handshake Failure (40) shown in the browser window as follows, Cannot communicate securely with peer: no common encryption algorithm(s). Error code: SSL_ERROR_NO_CYPHER_OVERLAP Chrome 69 offers the following "cipher suites", Reserved (GREASE) (0x7a7a) TLS_AES_128_GCM_SHA256 (0x1301) TLS_AES_256_GCM_SHA384 (0x1302) TLS_CHACHA20_POLY1305_SHA256 (0x1303) TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca9) TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c) TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d) TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) and the server elects to use something that I interpret as "RSA authentication, key exchange with AES/GCM encryption", TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d) Chrome shows a message in its Security tab, "The connection to this site uses TLS 1.2 (a strong protocol), RSA (an obsolete key exchange), and AES_256_GCM (a strong cipher)." The same is agreed with IE11 which offered the following list, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f) TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e) TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d) TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c) TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d) TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c) TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (0x006a) TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040) TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038) TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032) TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013) I wonder if (a) my choice of using RSA in a Certificate Signing Request conflicted with Mozilla's choice to not implement RSA authentication/exchange for the respective key encryption algorithms supported by BURP Enterprise and/or (b) BURP enterprise could implement the only encryption supported by Firefox when RSA authentication/exchange is used, AES/CBC?

PortSwigger Agent | Last updated: Sep 21, 2018 07:26AM UTC

Hi Ilguiz, Thanks for your feedback - I've had a quick try and it Firefox 62 is working okay for me on Mac and Windows - can I ask what platform you're installing Enterprise on? I believe the cipher suites that are supported by the server should include at least some of those on Firefox's list. Thanks very much, Mark

PortSwigger Agent | Last updated: Sep 24, 2018 12:40PM UTC

Hi Ilguiz, Just to say that we've now managed to replicate this issue on a Windows box and are currently looking into a fix. Thanks very much for your feedback on this! Cheers, Mark

PortSwigger Agent | Last updated: Sep 24, 2018 01:11PM UTC

Hi Ilguiz, We've managed to fix the problem and going forward (from the next release) we should support: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 TLS_ECDH_RSA_WITH_AES_128_CBC_SHA25 Thanks again for the report.

Burp User | Last updated: Sep 25, 2018 04:15PM UTC

I don't see TLS_RSA_WITH_AES_128_CBC_SHA or TLS_RSA_WITH_AES_256_CBC_SHA in the list. Will that prevent from using my RSA certificate from any browser?

PortSwigger Agent | Last updated: Sep 26, 2018 08:16AM UTC

Hi Ilguiz, I believe it should be okay - the cipher suites with 'RSA' in in should work for RSA certificates. I think the additional ECDH bit refers to additional "Forward Security". Please let us know if you have any difficulties when the next version is released. Thanks very much, Mark

PortSwigger Agent | Last updated: Oct 01, 2018 10:51AM UTC

Hi Ilguiz, To fix this issue we had to update the Java runtime that is shipped with Burp Enterprise - at the time we didn't have a mechanism to update the runtime for existing installations. This means that in order to fix an existing installation, you will need to run the 1.0.05 installer on the Enterprise Server (you can leave the data directory in place though, so you shouldn't lose scan data). However, we have just added a fix to allow the runtime to update automatically so when the next release comes out it should work without having to run the installer. Let me know if you have any problems with it. Thanks very much. Mark

Burp User | Last updated: Oct 05, 2018 12:26AM UTC

Version 1.0.05beta-869 shows the same behaviour with my RSA server certificate when using Firefox. Chrome shows a note in the development tools on the RSA as the obsolete key exchange, "The connection to this site uses TLS 1.2 (a strong protocol), RSA (an obsolete key exchange), and AES_256_GCM (a strong cipher)."

Burp User | Last updated: Jul 28, 2019 05:13PM UTC

Going forward, might i suggest looking into 3d spread spectrum encryption based off of a reversed timebase. It has not been created yet, but I have given you enough to wet your whistle and ponder. Thank you, James

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