Nessus Scans showed the following 3 vulnerabilities, they are related to need assistance to SSL Cert Loop back configuration.
Plugin Plugin Name
45411 SSL Certificate with Wrong Hostname
51192 SSL Certificate Cannot Be Trusted
57582 SSL Self-Signed Certificate
===============
SSL Certificate with Wrong Hostname (45411)
Synopsis: The SSL certificate for this service is for a different host.
Description: The 'commonName' (CN) attribute of the SSL certificate presented for this service is for a different machine.
Solution: Purchase or generate a proper certificate for this service.
================
SSL Certificate Cannot Be Trusted (51192)
Synopsis: The SSL certificate for this service cannot be trusted.
Description:
The server's X.509 certificate cannot be trusted. This situation can occur in three different ways, in which the chain of trust can be broken, as stated below :
- First, the top of the certificate chain sent by the server might not be descended from a known public certificate authority. This can occur either when the top of the chain is an unrecognized, self-signed certificate, or when intermediate certificates are missing that would connect the top of the certificate chain to a known public certificate authority.
- Second, the certificate chain may contain a certificate that is not valid at the time of the scan. This can occur either when the scan occurs before one of the certificate's 'notBefore' dates, or after one of the certificate's 'notAfter' dates.
- Third, the certificate chain may contain a signature that either didn't match the certificate's information or could not be verified. Bad signatures can be fixed by getting the certificate with the bad signature to be re-signed by its issuer. Signatures that could not be verified are the result of the certificate's issuer using a signing algorithm that Nessus either does not support or does not recognize.
If the remote host is a public host in production, any break in the chain makes it more difficult for users to verify the authenticity and identity of the web server. This could make it easier to carry out man-in-the-middle attacks against the remote host.
Solution: Purchase or generate a proper certificate for this service.
====================
SSL Self-Signed Certificate (57582)
Synopsis: The SSL certificate chain for this service ends in an unrecognized self-signed certificate.
Description: The X.509 certificate chain for this service is not signed by a recognized certificate authority. If the remote host is a public host in production, this nullifies the use of SSL as anyone could establish a man-in-the-middle attack against the remote host.
Note that this plugin does not check for certificate chains that end in a certificate that is not self-signed, but is signed by an unrecognized certificate authority.
Solution: Purchase or generate a proper certificate for this service.