|Applies To||RSA Product Set: RSA BSAFE|
RSA Product/Service Type: SSL-J
RSA Version/Condition: 6.2.x
|CVE ID||CVE-2016-7053, CVE-2016-7054, CVE-2016-7055, CVE-2016-8610|
|Article Summary||This article lists the impacts of four OpenSSL security vulnerabilities on the BSAFE SSL-J toolkit.|
|Link to Advisories||http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7053|
|Alert Impact||Not Exploitable|
|Technical Details||The flaw exists but it is not exploitable|
|Technical Details Explanation||This article addresses the impacts of the following four OpenSSL security vulnerabilities on the BSAFE SSL-J toolkit:|
CMS Null dereference (CVE-2016-7053): Applications parsing invalid CMS structures can crash with a NULL pointer dereference. This is caused by a bug in the handling of the ASN.1 CHOICE type in OpenSSL 1.1.0 which can result in a NULL value being passed to the structure callback if an attempt is made to free certain invalid encodings. Only CHOICE structures using a callback which do not handle NULL value are affected.
ChaCha20/Poly1305 heap-buffer-overflow (CVE-2016-7054): TLS connections using *-CHACHA20-POLY1305 ciphersuites are susceptible to a DoS attack by corrupting larger payloads. This can result in an OpenSSL crash. This issue is not considered to be exploitable beyond a DoS.
Montgomery multiplication may produce incorrect results (CVE-2016-7055): There is a carry propagating bug in the Broadwell-Specixfic Montgomery multiplication procedure that handles input lengths divisible by, but longer than 256 bits. Analysis suggests that attacks against RSA, DSA and DH private keys are impossible. This is because the subroutine in question is not used in operations with the private key itself and an input of the attacker's direct choice. Otherwise the bug can manifest itself as transient authentication and key negotiation failures or reproducible erroneous outcome of public-key operations with specially crafted input. Among EC algorithms only Brainpool P-512 curves are affected and one presumably can attack ECDH key negotiation. Impact was not analyzed in detail, because pre-requisites for attack are considered unlikely. Namely multiple clients have to choose the curve in question and the server has to share the private key among them, neither of which is default behavior. Even then only clients that chose the curve will be affected.
SSL-Death-Alert (CVE-2016-8610): The function "ssl3_read_bytes" in ssl/s3_pkt.c might lead to higher CPU usage due to improper handling of warning packets. An attacker could repeat the undefined plaintext warning packets of "SSL3_AL_WARNING" during the handshake, which will cause a 100% CPU usage on the server.
It has been determined that none of the four CVE’s listed above impact BSAFE SSL-J v6.2.X.
Read and use the information in this RSA Security Advisory to assist in avoiding any situation that might arise from the problems described herein. If you have any questions regarding this product alert, contact RSA Software Technical Support at 1- 800 995 5095. RSA Security LLC and its affiliates, including without limitation, its ultimate parent company, EMC Corporation, distributes RSA Security Advisories in order to bring to the attention of users of the affected RSA products, important security information. RSA recommends that all users determine the applicability of this information to their individual situations and take appropriate action. The information set forth herein is provided 'as is' without warranty of any kind. RSA disclaims all warranties, either express or implied, including the warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event, shall RSA, its affiliates or suppliers, be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if RSA, its affiliates or suppliers have been advised of the possibility of such damages. Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, so the foregoing limitation may not apply.