000036967 - RSA BSAFE SSL-J v6.2.4 False Positive Security Vulnerabilities

Document created by RSA Customer Support Employee on Jan 23, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036967
Applies ToRSA BSAFE SSL-J v6.2.4
CVE IDThe CVE IDs are listed in the table below.
Article SummaryThis article provides a list of security vulnerabilities that cannot be exploited on RSA BSAFE SSL-J v6.2.4, but which may be flagged by security scanners.
Link to AdvisoriesEach CVE ID listed can be searched using the following link: https://web.nvd.nist.gov/view/vuln/search. Once there, you can search for each CVE ID referenced in this article for more details.
Alert ImpactNot Exploitable
Alert Impact ExplanationFalse Positive
ResolutionThe vulnerabilities listed in the table below are in order by the date on which BSAFE Engineering determined that the SSL-J v6.2.4 was not vulnerable.
  

Embedded ComponentCVE IDSummary of VulnerabilityReason why Product is not VulnerableDate Determined False Positive
SSL-JCVE-2017-3730If a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this can result in the client attempting to dereference a NULL pointer leading to a client crash. This could be exploited in a Denial of Service attackSSL-J has a different implementation and the code checks for NULL objects.10/31/2018
SSL-JCVE-2017-3731If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. This issue affects OpenSSL SSL/TLS implementation when a truncated packet is received and one of the following cipher suites is used: CHACHA20, POLY1305, RC4-MD5.This version of SSL-J does not support CHACHA20 and POLY1305 cipher suites.  SSL-J does support RC4-MD5 cipher suites but our cryptographic implementation is different than that in OpenSSL.10/31/2018
SSL-JCVE-2017-3732There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL 1.0.2 before 1.0.2k and 1.1.0 before 1.1.0d. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline.For Java native implementations with dependency on Crypto-C ME, the implementation of the Montgomery multiplication is different to that outlined in CVE-2017-3732 and therefore not vulnerable.
  
   For native versions, the Dusse-Kalinski method of Montgomery multiplication is used.  This method is implemented at a higher level than assembly and incorporates overflow scenarios.
11/8/2018

 

 

Disclaimer

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, Dell EMC, 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.

Attachments

    Outcomes