OpenSSL 'ChangeCipherSpec' MiTM Vulnerability

[DCIM_Support]

When scanning a DCE 7.2.4 server a Open SSL MiTM Vulnerability occured.

Is this a known issue?

Below is a brief summary of the Vulnerability:

OpenSSL 'ChangeCipherSpec' MiTM Vulnerability
Description
The OpenSSL service on the remote host is vulnerable to a man-in-the-middle (MiTM) attack, based on its response to two consecutive 'ChangeCipherSpec' messages during the incorrect phase of an SSL/TLS handshake.

This flaw could allow a MiTM attacker to decrypt or forge SSL messages by telling the service to begin encrypted communications before key material has been exchanged, which causes predictable keys to be used to secure future traffic.

Note that Nessus has only tested for an SSL/TLS MiTM vulnerability (CVE-2014-0224). However, Nessus has inferred that the OpenSSL service on the remote host is also affected by six additional vulnerabilities that were disclosed in OpenSSL's June 5th, 2014 security advisory :

- An error exists in the function 'ssl3_read_bytes' that could allow data to be injected into other sessions or allow denial of service attacks. Note this issue is only exploitable if 'SSL_MODE_RELEASE_BUFFERS' is enabled. (CVE-2010-5298)

- An error exists related to the implementation of the Elliptic Curve Digital Signature Algorithm (ECDSA) that could allow nonce disclosure via the 'FLUSH+RELOAD' cache side-channel attack. (CVE-2014-0076)

- A buffer overflow error exists related to invalid DTLS fragment handling that could lead to execution of arbitrary code. Note this issue only affects OpenSSL when used as a DTLS client or server. (CVE-2014-0195)

- An error exists in the function 'do_ssl3_write' that could allow a null pointer to be dereferenced leading to denial of service attacks. Note this issue is exploitable only if 'SSL_MODE_RELEASE_BUFFERS' is enabled. (CVE-2014-0198)

- An error exists related to DTLS handshake handling that could lead to denial of service attacks. Note this issue only affects OpenSSL when used as a DTLS client.
(CVE-2014-0221)

- An unspecified error exists related to anonymous ECDH ciphersuites that could allow denial of service attacks. Note this issue only affects OpenSSL TLS clients. (CVE-2014-3470)

OpenSSL did not release individual patches for these vulnerabilities, instead they were all patched under a single version release. Note that the service will remain vulnerable after patching until the service or host is restarted.
Solution
OpenSSL 0.9.8 SSL/TLS users (client and/or server) should upgrade to 0.9.8za. OpenSSL 1.0.0 SSL/TLS users (client and/or server) should upgrade to 1.0.0m. OpenSSL 1.0.1 SSL/TLS users (client and/or server) should upgrade to 1.0.1h.
See Also
http://www.nessus.org/u?d5709faa
https://www.imperialviolet.org/2014/06/05/earlyccs.html
https://www.openssl.org/news/secadv_20140605.txt
Output

The remote service accepted an SSL ChangeCipherSpec message at an incorrect point in the handshake
leading to weak keys being used, and then attempted to decrypt an SSL record using those weak keys.

(CID:89555347)

[DCIM_Support]

Hello Edwin,

There is a KBase FA231276 that describes how this vulnerability (CVE-2014-0224) affects our products. To access our KBase, use the below link:

http://www.apc.com/site/support/index.cfm/faq/

Below is an excerpt of the KBase of how it affects DCE: 

Data Center Expert (DCE) is currently operating with OpenSSL v1.0.0 and is affected.

 This vulnerability can only be exercised if the receiving side to any OpenSSL communication is also a vulnerable version. While the typical communication between the DCE client and server does NOT use OpenSSL, and as such is not vulnerable to an attack, communications such as Alert Actions sent from the server are vulnerable to this issue. As such, this vulnerability can be mitigated simply by assuring the client side of the communication to DCE is operating at an OpenSSL version that is not vulnerable. In this way the limited amount of DCE data which uses OpenSSL will not be vulnerable.

 A version of Data Center Expert is currently in development and will resolve this vulnerability.

Hope this helps answer your question. 

Regards,

B

(CID:89555364)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.