SSL_ERROR_UNSUPPORTED_VERSION Work Around Firefox

The SSL_ERROR_UNSUPPORTED_VERSION error indicates that the website you are trying to visit uses an outdated and insecure version of the Transport Layer Security (TLS) protocol, which Chrome and Edge no longer support by default.

Firefox enforces a minimum of TLS 1.2 or higher for security, but you can use Firefox to get around this if you need to move forward.

If you understand the security risks and need to access the site, you can temporarily lower Firefox’s minimum required TLS version:

  1. In the Firefox address bar, type about:config and press Enter.
  2. Click Accept the Risk and Continue on the warning page.
  3. In the “Search preference name” box, type security.tls.version.min.
  4. Click the pencil icon next to the search result.
  5. Change the value from the default (which is likely 3 for TLS 1.2) to 1 (for TLS 1.0).
  6. Open the website in a new tab.

Revert this change by setting the value back to 3 as soon as you are done accessing the insecure website to ensure your browser remains secure for general browsing.

Fix For Warning SSL Medium Strength Cipher Suites Supported (SWEET32)

I recently ran into an issue where users were getting “SSL Medium Strength Cipher Suites Supported (SWEET32)” looking into the issue I found the following on the Nessus support site.

The remote host supports the use of SSL ciphers that offer medium-strength encryption. Nessus regards medium strength as any encryption that uses key lengths at least 64 bits and less than 112 bits, or else that uses the 3DES encryption suite.

To disable the Three DES ciphers run

https://www.nartac.com/Products/IISCrypto/

Click on best Best Practices

Under Ciphers

Uncheck Triples DES 168

Check Reboot and Hit Apply

The server will reboot and disable this protocol.

You must reboot for the changes to take effect.

I would recommend disabling protocals TLS 1.0 and 1.1 on your devices if you can for security purposes.

Uncheck TLS 1.0 and TLS 1.1 under Server Protocols

Check Reboot and Hit Apply

This will reboot the server for the changes to take effect.

With these 2 protocols disabled and the 3DES ciphers disabled, this warning should go away when you do your next scan.