[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ESA-2014-158: RSA BSAFE® Micro Edition Suite, SSL-J and SSL-C Triple Handshake Vulnerability
- To: "'bugtraq@xxxxxxxxxxxxxxxxx'" <bugtraq@xxxxxxxxxxxxxxxxx>, "'dm@xxxxxxxxxxxxxxxxx'" <dm@xxxxxxxxxxxxxxxxx>
- Subject: ESA-2014-158: RSA BSAFE® Micro Edition Suite, SSL-J and SSL-C Triple Handshake Vulnerability
- From: Security Alert <Security_Alert@xxxxxxx>
- Date: Wed, 4 Feb 2015 14:08:47 +0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ESA-2014-158: RSA BSAFE® Micro Edition Suite, SSL-J and SSL-C Triple Handshake
Vulnerability
EMC Identifier: ESA-2014-158
CVE Identifier: CVE-2014-4630
Severity Rating: CVSS v2 Base Score: 6.8 (AV:N/AC:M/Au:N/C:P/I:P/A:P)
Affected Products:
RSA BSAFE Micro Edition Suite (MES) all 4.0.x versions prior to 4.0.6
RSA BSAFE SSL-J all versions prior to 6.1.4
RSA BSAFE SSL-C all versions
Unaffected Products:
RSA BSAFE MES 4.0.6 and 4.1
RSA BSAFE SSL-J 6.1.4
Summary:
RSA BSAFE Micro Edition Suite and SSL-J contain updates designed to prevent
Triple Handshake attacks (CVE-2014-4630). For SSL-C, a work around is provided
to prevent this attack.
Details:
There is a known potential vulnerability in the TLS protocol where it is
possible for a malicious server to impersonate a client to another server using
the client?s credentials and successfully perform a man-in-the-middle attack on
the third handshake. See original advisory for more details:
https://www.secure-resumption.com/
MES 4.1, MES 4.0.6 and SSL-J 6.1.4 are designed to include a fix which
disallows a change of server certificate when renegotiating. This vulnerability
can be avoided in SSL-C 2.8.x by disabling TLS renegotiation.
Recommendation:
RSA recommends that customers on MES 4.0.x upgrade to MES 4.0.6 or to MES 4.1
and those on SSL-J 5.1.x and SSL-J 6.x upgrade to SSL-J 6.1.4 at the earliest
opportunity.
For customers using SSL-C 2.8.x, RSA recommends disabling TLS renegotiation.
Instructions on how to disable TLS renegotiation can be obtained from the
product documentation or by contacting RSA Customer Support.
Credits:
The Triple Handshake attack was originally found by Antoine Delignat-Lavaud,
Karthikeyan Bhargavan and Alfredo Pironti from the Prosecco research team at
INRIA Paris-Rocquencourt.
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
RSA, The Security Division of EMC, distributes SCOL 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 disclaim 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 or its suppliers be liable for any
damages whatsoever including direct, indirect, incidental, consequential, loss
of business profits or special damages, even if RSA or its suppliers have been
advised of the possibility of such damages. Some states 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)
iEYEARECAAYFAlTSJ4YACgkQtjd2rKp+ALxeGwCeNNq5oKzdpDtMByfCrkm6WMux
Da4AoNxuiuY9bUX0vgDK51/z82Ql7Nu+
=YBzf
-----END PGP SIGNATURE-----