000035679 - RSA BSAFE MES (Micro Edition Suite) v4.1.6 False Positive Security Vulnerabilities

Document created by RSA Customer Support Employee on Mar 20, 2018Last modified by RSA Customer Support Employee on Jan 23, 2019
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000035679
Applies ToRSA BSAFE MES v4.1.6
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 MES v4.1.6, 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 MES v4.1.6 was not vulnerable.
Embedded ComponentCVE IDSummary of VulnerabilityReason why Product is not VulnerableDate Determined False Positive
MESCVE-2017-3735While parsing an IPAddressFamily extension in an X.509 certificate, it is possible to do a one-byte overread. This would result in an incorrect text display of the certificate. This bug has been present since 2006 and is present in all versions of OpenSSL since then.MES does not support and process IP Address x.509 extensions as defined in RFC 3779 and CVE-2017-3735 is an implementation specific issue which affects only the OpenSSL code. 9/12/2017
MESCVE-2018-0733Because of an implementation bug the PA-RISC CRYPTO_memcmp function is effectively reduced to only comparing the least significant bit of each byte. This allows an attacker to forge messages that would be considered as authenticated in an amount of tries lower than that guaranteed by the security claims of the scheme. The module can only be compiled by the HP-UX assembler, so that only HP-UX PA-RISC targets are affected.The OpenSSL change is in HP PA RISC optimized implementation of CRYPTO_memcmp, openssl-1.1.0h/crypto/pariscid.pl line 163
   The change was to extract a 1 bit field from the most significant bit instead of the least significant bit of the 32 bit word. Specifically:
                   extru           %r29,31,1,$rv     =>     extru           %r29,0,1,$rv
   The OpenSSL C implementation was unchanged in this revision, and was unaffected.
   NOTE: No v3.2.4 - v4.1.x versions of MES are affected.



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.