|Category:||SSL and TLS|
|Title:||SSL/TLS: Certificate Signed Using A Weak Signature Algorithm|
|Summary:||The remote service is using a SSL/TLS certificate in the certificate chain that has been signed using a; cryptographically weak hashing algorithm.|
The remote service is using a SSL/TLS certificate in the certificate chain that has been signed using a
cryptographically weak hashing algorithm.
The following hashing algorithms used for signing SSL/TLS certificates are considered cryptographically weak
and not secure enough for ongoing use:
- Secure Hash Algorithm 1 (SHA-1)
- Message Digest 5 (MD5)
- Message Digest 4 (MD4)
- Message Digest 2 (MD2)
Beginning as late as January 2017 and as early as June 2016, browser developers such as Microsoft and Google will begin warning users when visiting
web sites that use SHA-1 signed Secure Socket Layer (SSL) certificates.
NOTE: The script preference allows to set one or more custom SHA-1 fingerprints of CA certificates which are trusted by this routine. The fingerprints
needs to be passed comma-separated and case-insensitive:
Servers that use SSL/TLS certificates signed with a weak SHA-1, MD5, MD4 or MD2 hashing algorithm will need to obtain new
SHA-2 signed SSL/TLS certificates to avoid web browser SSL/TLS certificate warnings.
|Copyright||Copyright (C) 2016 Greenbone Networks GmbH|
|This is only one of 87302 vulnerability tests in our test suite. Find out more about running a complete security audit.|
To run a free test of this vulnerability against your system, register below.