Windows 10: SSL Certificate Signed Using Weak Hashing Algorithm

Sandeep Kumar Reddy · Mar 16, 2022

Tenable Scan provides the below report but i dont see any certificate with MD2, MD4, MD5, or SHA1. Could you please advise the fix for this case?An SSL certificate in the certificate chain has been signed using a weak hash algorithm.The remote service uses an SSL certificate chain that has been signed using a cryptographically weak hashing algorithm e.g. MD2, MD4, MD5, or SHA1. These signature algorithms are known to be vulnerable to collision attacks. An attacker can exploit this to generate another certificate with the same digital signature, allowing an attacker to masquerade as the affec

:)

Brink · Mar 16, 2022

Deprecation of SHA-1 for SSL/TLS Certificates in Microsoft Edge & IE11

Microsoft Security Advisory 4010323

Deprecation of SHA-1 for SSL/TLS Certificates in Microsoft Edge and Internet Explorer 11
Published: May 9, 2017
Version: 1.0

Executive Summary

Beginning May 9, 2017, Microsoft released updates to Microsoft Edge and Internet Explorer 11 to block sites that are protected with a SHA-1 certificate from loading and to display an invalid certificate warning. This change will only impact SHA-1 certificates that chain to a root in the Microsoft Trusted Root Program where the end-entity certificate or the issuing intermediate uses SHA-1. Enterprise or self-signed SHA-1 certificates will not be impacted, although we recommend that all customers quickly migrate to SHA-2 based certificates. For more information, please see Windows Enforcement of SHA1 Certificates.

For more information see Microsoft Knowledge Base Article 4010323.

Advisory Details

Issue References
For more information about this issue, see the following references:

[table][tr][td]References[/td] [td]References[/td] [/tr] [tr][td]General Information[/td] [td]Windows Enforcement of SHA1 Certificates[/td] [/tr] [tr][td][/td] [td]SHA-1 deprecation countdown[/td] [/tr] [tr][td]Technical Requirements[/td] [td]Protecting Against Weak Cryptographic Algorithms[/td] [/tr] [/table]

Affected Software

This advisory applies to the following operating systems:

[table][tr][td]Windows 7[/td] [/tr] [tr][td]Windows 7 for 32-bit Systems Service Pack 1[/td] [/tr] [tr][td]Windows 7 for x64-based Systems Service Pack 1[/td] [/tr] [tr][td]Windows Server 2008 R2[/td] [/tr] [tr][td]Windows Server 2008 R2 for x64-based Systems Service Pack 1[/td] [/tr] [tr][td]Windows Server 2008 R2 for Itanium-based Systems Service Pack 1[/td] [/tr] [tr][td]Windows 8.1[/td] [/tr] [tr][td]Windows 8.1 for 32-bit Systems[/td] [/tr] [tr][td]Windows 8.1 for x64-based Systems[/td] [/tr] [tr][td]Windows Server 2012 R2[/td] [/tr] [tr][td]Windows Server 2012 R2[/td] [/tr] [tr][td]Windows 10[/td] [/tr] [tr][td]Windows 10 for 32-bit Systems[/td] [/tr] [tr][td]Windows 10 for x64-based Systems[/td] [/tr] [tr][td]Windows 10 Version 1511 for 32-bit Systems[/td] [/tr] [tr][td]Windows 10 Version 1511 for x64-based Systems[/td] [/tr] [tr][td]Windows 10 Version 1607 for 32-bit Systems[/td] [/tr] [tr][td]Windows 10 Version 1607 for x64-based Systems[/td] [/tr] [tr][td]Windows Server 2016[/td] [/tr] [tr][td]Windows Server 2016 for x64-based Systems[/td] [/tr] [tr][td]Server Core installation option[/td] [/tr] [tr][td]Windows Server 2008 R2 for x64-based Systems (Server Core installation)[/td] [/tr] [tr][td]Windows Server 2012 R2 (Server Core installation)[/td] [/tr] [tr][td]Windows Server 2016 for x64-based Systems (Server Core installation)[/td] [/tr] [/table]

Advisory FAQ

What is the scope of the advisory?
This advisory aims to assist customers in assessing the risk of certain applications that use X.509 digital certificates that are signed using the SHA-1 hashing algorithm and to recommend that administrators and certificate authorities use SHA-2 in place of SHA-1 as an algorithm for signing digital certificates.

Is this a security vulnerability that requires Microsoft to issue a security update?
No. Microsoft recommends that all customers migrate to SHA-2, and the use of SHA-1 as a hashing algorithm for signing purposes is discouraged and is no longer a best practice. Although this is not a vulnerability in a Microsoft product, Microsoft is issuing this advisory to help clarify the actual risk involved to customers.

What causes this threat?
The root cause of the problem is a known weakness of the SHA-1 hashing algorithm that exposes it to collision attacks. Such attacks could allow an attacker to generate additional certificates that have the same digital signature as an original. The use of SHA-1 certificates for specific purposes that require resistance against these attacks is discouraged. At Microsoft, the Security Development Lifecycle has required Microsoft to no longer use the SHA-1 hashing algorithm as a default in Microsoft software. For more information about SHA-1 collision weakness, see SHAttered: The first collision for full SHA-1.

What is a digital certificate?
In public key cryptography, one of the keys, known as the private key, must be kept secret. The other key, known as the public key, is intended to be shared with the world. However, there must be a way for the owner of the key to tell the world who the key belongs to. Digital certificates provide a way to do this. A digital certificate is an electronic credential used to certify the online identities of individuals, organizations, and computers. Digital certificates contain a public key packaged together with information about it - who owns it, what it can be used for, when it expires, and so forth. For more information, see Understanding Digital Certificates.

What is the purpose of a digital certificate?
Digital certificates are used primarily to verify the identity of a person or device, authenticate a service, or encrypt files. Normally, there is no need to think about certificates at all, aside from the occasional message stating that a certificate is expired or invalid. In such cases, one should follow the instructions provided in the message.

What is a certification authority (CA)?
Certification authorities are the organizations that issue certificates. They establish and verify the authenticity of public keys that belong to people or other certification authorities, and they verify the identity of a person or organization that asks for a certificate.

Suggested Actions

Review Microsoft Trusted Root Program Policy ChangesCustomers who are interested in learning more about the topic covered in this advisory should review Windows Enforcement of SHA1 Certificates.

Update from SHA-1 to SHA-2Certificate authorities have been prohibited from issuing new SHA-1 certificates Since January 2016. Customers should ensure that their certificate authorities are using the SHA-2 hashing algorithm to obtain SHA-2 certificates from their certificate authorities. To sign code with SHA-2 certificates, see the guidance on this topic at Windows Enforcement of SHA1 Certificates.
Impact of action: Older hardware-based solutions may require upgrading to support these newer technologies.

Keep Windows UpdatedAll Windows users should apply the latest Microsoft security updates to help make sure that their computers are as protected as possible. If you are not sure whether your software is up to date, visit Windows Update, scan your computer for available updates, and install any high-priority updates that are offered to you. If you have Automatic Updates enabled, the updates are delivered to you when they are released, but you have to make sure you install them.

Other Information

Feedback

You can provide feedback by completing the Microsoft Help and Support form, Customer Service Contact Us.

Support

Customers in the United States and Canada can receive technical support from Security Support. For more information, see Microsoft Help and Support.

International customers can receive support from their local Microsoft subsidiaries. For more information, see International Support.

Microsoft TechNet Security provides additional information about security in Microsoft products.

Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions

V1.0 (May 9, 2017): Advisory published.

Click to expand...

Source: Microsoft Security Advisory 4010323

Anthony Gal · Mar 16, 2022

ssl certificates

Hi Richard,

This error message SSL certificates could have happened due to several reasons like browser security certificates or outdated browser. We would like to know more about the issue by asking the following questions below:

Have you tried deleting and clear the cache?

What browser are you using?

Have you tried using another browser?

Have you tried contacting your software developer?

We look forward to your response to our queries.

tonydavies---01 · Mar 16, 2022

Self Signed Certificates for SSL connections

Hi, Thanks for the idea.

I have just tried that, and unfortunately - still got the same problem!

The Nokia just does not accept the existence of the certificate - even though it appears in the certificate store, and appears to be correctly configured.

Can't believe that Nokia have not been flooded with similar complaints if this occurs to anyone who tries to sync with MS Exchange via SSL.

Any other suggestions will be greatfully received!

Windows 10: SSL Certificate Signed Using Weak Hashing Algorithm

SSL Certificate Signed Using Weak Hashing Algorithm

SSL Certificate Signed Using Weak Hashing Algorithm

SSL Certificate Signed Using Weak Hashing Algorithm

SSL Certificate Signed Using Weak Hashing Algorithm - Similar Threads - SSL Certificate Signed

Corrupted SSL Certificates

Corrupted SSL Certificates

Persistent errors with certificate hash algorithm selection on IKEv2 VPN with updated...

Persistent errors with certificate hash algorithm selection on IKEv2 VPN with updated...

Config Hash algorithm for HLK Studio

Config Hash algorithm for HLK Studio

Config Hash algorithm for HLK Studio

SSL Certificate Signed Using Weak Hashing Algorithm

SSL Certificate Signed Using Weak Hashing Algorithm