[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ESA-2016-013: RSA BSAFE® Micro Edition Suite, Crypto-C Micro Edition, Crypto-J, SSL-J and SSL-C Lenstra’s Attack Vulnerability



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ESA-2016-013: RSA BSAFE® Micro Edition Suite, Crypto-C Micro Edition, Crypto-J, SSL-J and SSL-C Lenstra?s Attack Vulnerability


EMC Identifier: ESA-2016-013
 
CVE Identifier: CVE-2016-0887
 
Severity Rating: CVSS v3 Base Score: 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)                                          
 
Affected Products: 
·         RSA BSAFE Micro Edition Suite (MES) all 4.1.x versions prior to 4.1.5
·         RSA BSAFE Micro Edition Suite (MES) all 4.0.x versions
·         RSA BSAFE Crypto-C Micro Edition (CCME) all 4.1.x versions prior to 4.1.3
·         RSA BSAFE Crypto-C Micro Edition (CCME) all 4.0.x versions
·         RSA BSAFE Crypto-J all versions prior to 6.2.1
·         RSA BSAFE SSL-J all versions prior to 6.2.1
·         RSA BSAFE SSL-C all versions including 2.8.9
 
Unaffected Products:
·         RSA BSAFE Micro Edition Suite (MES) 4.1.5
·         RSA BSAFE Crypto-C Micro Edition (CCME) 4.1.3
·         RSA BSAFE Crypto-J 6.2.1
·         RSA BSAFE SSL-J 6.2.1
 
Summary: 
RSA BSAFE® Micro Edition Suite, Crypto-C Micro Edition, Crypto-J and SSL-J contain a fix to address Lenstra?s attack.
 
Details: 
An undetected error during a PKCS #1 v1.5 RSA signature operation using CRT private values can potentially leak a private key prime via a side channel attack.
For TLS/SSL capable toolkits an attack is carried out by attempting to establish a TLS connection to a server that implements the ServerKeyExchange message during the handshake process, negotiate Perfect Forward Secrecy and look for the ServerKeyExchange message to report a failure due to an incorrectly computed signature. Once a signature failure is reported, the RSA private key data can be recovered (similar to CVE-2015-0478).
 
Recommendation:
·         RSA BSAFE Micro Edition Suite (MES) 4.1.5 contains a fix for CVE-2016-0887
·         RSA BSAFE Crypto-C Micro Edition (CCME) 4.1.3 contains a fix for CVE-2016-0887
·         RSA BSAFE Crypto-J 6.2.1 contains a fix for CVE-2016-0887
·         RSA BSAFE SSL-J 6.2.1 contains a fix for CVE-2016-0887
 
RSA recommends affected customers upgrade to the versions listed above at the earliest opportunity.
 
RSA recommends all RSA BSAFE SSL-C customers upgrade to RSA BSAFE Micro Edition Suite (MES) as per previous notifications about the End Of Life (EOL) for RSA BSAFE SSL-C.
 
The following workaround is available for CVE-2016-0887.
 
It is recommended that applications verify all RSA signature creation. This includes when creating a signature with the sign APIs as well as signing certificates, CRLs, OCSP responses and CMS messages.
 
When using TLS in a server with an RSA certificate, the following option is available: Change the server PKI to a DSA cert and use TLS_DHE_DSS_* cipher suites.
 
NOTE: Servers using TLS_RSA_* cipher suites perform RSA decrypt operation and are not vulnerable but do not have Perfect Forward Secrecy.
 
 [The following is standard text included in all security advisories.  Please do not change or delete.]
 
Severity Rating:
 
For an explanation of Severity Ratings, refer to the Knowledge Base Article, ?Security Advisories Severity Rating? at https://knowledge.rsasecurity.com/scolcms/knowledge.aspx?solution=a46604. RSA recommends all customers take into account both the base score and any relevant temporal and environmental scores which may impact the potential severity associated with particular security vulnerability.
 
Obtaining Downloads:
To request your upgrade of the software, please call your local support telephone number (contact phone numbers are available at http://www.emc.com/support/rsa/contact/index.htm) for most expedient service.    

Obtaining Documentation:
To obtain RSA documentation, log on to RSA SecurCare Online at https://knowledge.rsasecurity.com and click Products in the top navigation menu. Select the specific product whose documentation you want to obtain. Scroll to the section for the product version that you want and click the set link.

Severity Rating:
For an explanation of Severity Ratings, refer to the Knowledge Base Article, ?Security Advisories Severity Rating? at https://knowledge.rsasecurity.com/scolcms/knowledge.aspx?solution=a46604. RSA recommends all customers take into account both the base score and any relevant temporal and environmental scores which may impact the potential severity associated with particular security vulnerability.

Obtaining More Information:
For more information about RSA products, visit the RSA web site at http://www.rsa.com.

Getting Support and Service:
For customers with current maintenance contracts, contact your local RSA Customer Support center with any additional questions regarding this RSA SecurCare Note. For contact telephone numbers or e-mail addresses, log on to RSA SecurCare Online at https://knowledge.rsasecurity.com, click Help & Contact, and then click the Contact Us - Phone tab or the Contact Us - Email tab.

General Customer Support Information:
http://www.emc.com/support/rsa/index.htm

RSA SecurCare Online:
https://knowledge.rsasecurity.com

EOPS Policy:
RSA has a defined End of Primary Support policy associated with all major versions. Please refer to the link below for additional details. 
http://www.emc.com/support/rsa/eops/index.htm

SecurCare Online Security Advisories
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, distribute 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 its 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 its 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.

About RSA SecurCare Notes & Security Advisories Subscription
RSA SecurCare Notes & Security Advisories are targeted e-mail messages that RSA sends you based on the RSA product family you currently use. If you?d like to stop receiving RSA SecurCare Notes & Security Advisories, or if you?d like to change which RSA product family Notes & Security Advisories you currently receive, log on to RSA SecurCare Online at https://knowledge.rsasecurity.com/scolcms/help.aspx?_v=view3. Following the instructions on the page, remove the check mark next to the RSA product family whose Notes & Security Advisories you no longer want to receive. Click the Submit button to save your selection.

Sincerely,
RSA Customer Support
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)

iEYEARECAAYFAlcL864ACgkQtjd2rKp+ALymcQCeKTDYkPRyPsXJ51agIyT9pzhs
DkoAoL5xx2e0opkTIOtucgldIM11gJh3
=GZX6
-----END PGP SIGNATURE-----