JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
According to Qualys SSL Labs testing, secure.jotform.co is vulnerable. When will this be fixed?Asked by UnLitho on December 12, 2014 at 07:02 PM
It appears that there are some vulnerabilities in the SSL certificate protecting secure.jotform.co. Perhaps this can be looked into and an estimated fix time be posted?
Screenshot of the results: http://i.imgur.com/XD8jRtb.jpg
- Server is vulnerable to the OpenSSL CCS vulnerability (CVE-2014-0224) and is exploitable (since June!)
- Server uses SHA1 when it should be using more secure SHA2 (at least SHA256 recommended). Google Chrome will be warning users of sites protected with SHA1 certificates that the site they're visiting is unsafe starting sometime soon, maybe as later as early next year.
Thank you for this information.
I was also able to see the same issue on my browser when browsing on https://www.jotform.com
I will forward this thread to our back-end team support so that they can properly checked the problem.
We will inform you here for any update on the status.
Chief Technology Officer
Problem has been fixed,
Thanks for the quick resolution to that! Good to see things looking more secure. Do you know if when the certificate expires in 2 months, it is going to be renewed with at least SHA2withRSA? Chrome will soon be showing SHA1 certificate-protected sites as potentially insecure.
I honestly don't know if our higher ups would consider upgrading to SHA2, but I have forwarded this thread to EEE. I'm sure they will if that will affect our system.
The following is conveniently copied for its examples from here.
As of late 2014, SHA1 certificates and it’s SHA1 trust chain (not including the Root CA) will be considered insecure by Google Chrome.
A three step process will increase the severity of the warning:
1. Initially SHA1 certificates that expire on/after 2017/1/1, and which contain SHA-1-based signatures in the validated chain, will be shown the “Secure, but minor errors” icon. This is a lock with a yellow triangle
2. Severity will increase thereafter, where:
SHA1 certificates that expire between 2016/6/1 and 2016/12/31, inclusively, and which contain SHA-1-based signatures in the validated chain, will be shown the “Secure, but minor errors” icon. This is a lock with a yellow triangle. SHA1 certificates that expire on/after 2017/1/1, and which contain SHA-1-based signatures in the validated chain, will be shown the “Neutral, no security” icon. This is the blank page icon, as shown by HTTP URLs.
3. Finally Chrome will render websites with SHA1 certificates that expire on/after 2017/1/1 and which contain SHA-1-based signatures in the validated chain, with the “Affirmatively insecure, major errors” icon. The “Affirmatively insecure, major errors” icon is a lock with a red X.
To resolve this issue SHA2 certificates must be installed.
Considering your certificate expires in the next few months, it might be convenient to go ahead and have them renew at SHA2 and get that done and over with.
Thank you for providing more details.
I have instead created a separate topic for the new suggestion here http://www.jotform.com/answers/478725
We will attend to it as soon as we can.