Benches macOS

1

Problems with a vulnerability

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hi,

I'm scanning my systems using QualysGuard appliances and I reported the following vulnerability between SSL and Server Admin but I can't resolve it ...

--

*--SSL Server Allows Anonymous Authentication Vulnerability port 311/tcp over SSL*

QID: 38142 CVSS Base: 5.1 [1]

Category: General remote services CVSS Temporal: 3.8

CVE ID: -

Vendor Reference: -

Bugtraq ID: -

Modified: 07/07/2008

Edited: No

THREAT:

The Secure Socket Layer (SSL) protocol allows for secure communication between a client and a server. The client usually authenticates the server using an

algorithm like RSA or DSS. Some SSL ciphers allow SSL communication without authentication. Most common Web browsers like Microsoft Internet Explorer,

Netscape and Mozilla do not use anonymous authentication ciphers by default.

A vulnerability exists in SSL communcations when clients are allowed to connect

Scan Results page 4

using no authentication algorithm. SSL client-server communication may use several different types of

authentication: RSA, Diffie-Hellman, DSS or none. When 'none' is used, the

communications are vulnerable to a man-in-the-middle attack."

IMPACT:

An attacker can exploit this vulnerability to impersonate your server to clients.

SOLUTION:

Disable support for anonymous authentication.

1) Apache:

Typically, for Apache/mod_ssl, httpd.conf or ssl.conf should have the following lines:

SSLProtocol -ALL +SSLv3 +TLSv1

SSLCipherSuite ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4
RSA:+HIGH:MEDIUM

For Apache/apache_ssl include the following line in the configuration file (httpsd.conf):

SSLRequireCipher ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4
RSA:+HIGH:MEDIUM

2) IIS:

For IIS please see: How to disable PCT 1.0, SSL 2.0, SSL 3.0, or TLS 1.0 in Internet Information Services (
http://support.microsoft.com/kb/187498/en-us), How to

Restrict the Use of Certain Cryptographic Algorithms and Protocols in Schannel.dll (
http://support.microsoft.com/kb/245030/en-us), How to Determine the Cipher

Suite for the Server and Client (
http://support.microsoft.com/kb/299520/en-us), , and How to restrict the use of certain ciphers in Internet Information Services 5.0

(
http://support.microsoft.com/kb/241447)

3) Wu-FTP:

For Wu-FTP which supports TLS, the ciphers parameter in TLS configuration file should be set to -ALL +SSLv3 +TLSv1 For more details please consult the

docs/HOWTO/ssl
and_tlsftpd.HOWTO file provided by wu-ftpd distribution.

Additional reading:

http://www.cisco.com/web/about/ac123/ac147/archivedissues/ipj1-1/ssl.html (
http://www.cisco.com/web/about/ac123/ac147/archivedissues/ipj1-1/ssl.html)

http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#sslciphersuite (
http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#sslciphersuite)

http://www.megasecurity.org/Info/ssl_servers.html (
http://www.megasecurity.org/Info/ssl_servers.html)

I dont have SSL enable in Apache ... I think that the problems is in Server Admin and SSL comunication that permits anonymous connection????

Any clue to try resolve it?

Thanks for your help!

1 reply

Sign in or join Beachball Help to reply.

  1. 0

    Peter Scordamaglia

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    1: My first inclination is that this is a non-issue. The vulnerability you are concerned with 'SSL Server Allows Anonymous Authentication Vulnerability port 311/tcp over SSL' is for port 311, a port that is not normally set to allow access to the internet. So any vulnerability/data leak would be from internal.

    2: That port is for access from Server Admin.app. Yes, the port is held open and connectivity via any access (such as telnet localhost 311) does connect, there is no data/information leakage that I could cause. That port does not respond to standard queries such as help, info, ? et al. I would suspect it would have to be a crafted xml/soap or somesuch conversation before anything could potentially leak.

    3: Assuming that access to this data needs to be the same as what happens when one uses Server Admin.app, the data probably could be considered secure as in order to view or modify any data, you must know a valid user id and password and that user must be authorized as an administrator (or monitor) account before the Server Admin.app will allow control.

    If you are still concerned, you could submit this as a bug to
    https://bugreport.apple.com/ . Be aware you must be an ADC member to submit bugs.

    Peter