AFS Security Team has sited the following vulnerabilities for DevTest servers:
Wrong Hostname, Protocol: TCP Port: 2010
The SSL certificate for this service is for a different host.
There are 2 ways to solve it:
1. In the scanning tool, we can add the DevTest certificates under the trusted certs. And continue to use the self-signed certs with DevTest.
OR
2. To use a certificate issued by a trusted or private Certificate Authority and add it to the the keystore files in DevTest and this cert will be used by DevTest during SSL connections.
These are the keystores/truststores we deliver with DevTest:
Note that certificates in the chain that are contained in the Nessus CA database (known_CA.inc) have been ignored."
Contact the Certificate Authority to have the certificate reissued.
http://tools.ietf.org/html/rfc3279
http://www.nessus.org/u?e120eea1
http://technet.microsoft.com/en-us/security/advisory/961509