Error Message

Excerpt of Nessus report pertaining to VOM.

Port www (5634/tcp)

SSL Certificate Cannot Be Trusted

Synopsis :

The SSL certificate for this service cannot be trusted.

Description :

The server's X.509 certificate does not have a signature from a known
public certificate authority. This situation can occur in three
different ways, each of which results in a break in the chain below
which certificates cannot be trusted.

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 was not possible to
verify. 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 nullifies the use of SSL as anyone could establish a man in the
middle attack against the remote host.

Solution :

Purchase or generate a proper certificate for this service.

(Symantec note: please see the Symantec Solution regarding the  certificate)

Risk factor :

Medium / CVSS Base Score : 6.4
(CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:N)

Plugin output :
The following certificates were at the top of the certificate
chain sent by the remote host, but are signed by an unknown
certificate authority :

Subject : CN=root/OU=xxxxxx.xxxxxx.com/O=localhost
Issuer : CN=root/OU=xxxxxx.xxxxxx.com/O=localhost

Nessus ID : 51192

SSL Self-Signed Certificate

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.

(Symantec note: please see the Symantec Solution regarding the  certificate)

Risk factor :

Medium / CVSS Base Score : 6.4
(CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:N)

Plugin output :
The following certificate was found at the top of the certificate
chain sent by the remote host, but is self-signed and was not
found in the list of known certificate authorities :

|-Subject : CN=root/OU=xxxxxx.xxxxxx.com/O=localhost

Nessus ID : 57582http://www.nessus.org/plugins/index.php?view=single&id=57582

Plugin: 53491
Plugin Name: SSL / TLS Renegotiation DoS
 

Synopsis: The remote service allows repeated renegotiation of TLS / SSL
connections.

Description: The remote service encrypts traffic using TLS / SSL and
permits clients to renegotiate connections. The computational
requirements for renegotiating a connection are asymmetrical between the
client and the server, with the server performing several times more work.

Since the remote host does not appear to limit the number of
renegotiations for a single TLS / SSL connection, this permits a client to
open several simultaneous connections and repeatedly renegotiate them,
possibly leading to a denial of service condition.

Solution: Contact the vendor for specific patch information.
See Also: http://www.ietf.org/mail-archive/web/tls/current/msg07553.html

Risk Factor: Medium
CVSS Base Score: 4.3
CVSS Vector: CVSS2#AV:N/AC:M/Au:N/C:N/I:N/A:P
CVSS Temporal Score: 3.9
CVSS Temporal Vector: CVSS2#E:POC/RL:U/RC:C

Plugin Output:
The remote host is vulnerable to renegotiation DoS over TLSv1 / SSLv3.
CVE: CVE-2011-1473
BID: 48626
Crossref: OSVDB #73894
Vulnerability Publication Date: 2011/03/13
Plugin Publication Date: 2011/05/04
Plugin Modification Date: 2012/11/15
Exploit Available: true
Exploitability Ease: Exploits are available
Plugin Type: remote
Source File: ssl_renegotiation_dos.nasl

Nessus is unfamiliar with VOM design.

Please consider the following points regarding the use of the VOM product.

1)  While the Nessus report suggests purchasing or generating a certificate:

 This is not necessary and cannot be implemented in the current structure of the product.  Also, see next point.

2)  A 128 bit self signed certificate is used.  While this certificate is not issued by a known public authority, it is generated by a Veritas product during configuration and can be trusted. 

3)   VOM uses secure HTTPS protocol on port 5634 to communicate between hosts in the VOM domain.  Each host (Central Server and Managed Hosts) will have an xprtld process which is a lite web server that will use HTTPS protocol on this port for host to host communications.

4)  This is not a very serious vulnerability, it is a denial of service attack where the client constantly renegotiates the SSL encryption. However, a client can just open multiple connections to an SSL server and then disconnect. Each connection also negotiates the SSL encryption, and this is just as costly, so even if there is a way to stop renegotiation there are other denial of service attacks that are just based on connecting over and over.
These do not expose any information or grant any access.
 

Applies To

VOM 4.1

VOM 5.0

VOM 6.0