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

ESA-2013-032 RSA BSAFE® Micro Edition Suite Security Update for SSL/TLS Plaintext Recovery (aka “Lucky Thirteen”) Vulnerability



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

ESA-2013-032: RSA BSAFE® Micro Edition Suite Security Update for SSL/TLS 
Plaintext Recovery (aka ?Lucky Thirteen?) Vulnerability


EMC Identifier: ESA-2013-032


CVE Identifier: CVE-2013-0169


Severity Rating: CVSS v2 Base Score: 2.6 (AV:N/AC:H/Au:N/C:P/I:N/A:N)

 

Affected Products:

All versions of RSA BSAFE Micro Edition Suite except for 4.0.3 and 3.2.5

 

Unaffected Products:

RSA BSAFE Micro Edition Suite 4.0.3 and 3.2.5 (newly released)

 

Summary:  

RSA BSAFE Micro Edition Suite 4.0.3 and 3.2.5 contain updates designed to 
prevent SSL/TLS Plaintext Recovery (aka Lucky Thirteen) attacks (CVE-2013-0169).

 

Details:  

Researchers have discovered a weakness in the handling of CBC cipher suites in 
SSL, TLS and DTLS. The ?Lucky Thirteen? attack exploits timing differences 
arising during MAC processing. Vulnerable implementations do not properly 
consider timing side-channel attacks on a MAC check requirement during the 
processing of malformed CBC padding, which allows remote attackers to conduct 
distinguishing attacks and plaintext-recovery attacks via statistical analysis 
of timing data for crafted packets, aka the "Lucky Thirteen" issue.

 
Details of this attack can be found at: 
http://www.isg.rhul.ac.uk/tls/TLStiming.pdf
 


Recommendation:
 

RSA BSAFE Micro Edition Suite 4.0.3 and 3.2.5 contain a patch that is designed 
to help ensure that MAC checking is time invariant in servers. 

 

RSA recommends that customers on RSA BSAFE Micro Edition Suite 3.2.x or lower 
upgrade to RSA BSAFE Micro Edition Suite 3.2.5.   RSA recommends that customers 
on RSA BSAFE Micro Edition Suite 4.0.x upgrade to RSA BSAFE Micro Edition Suite 
4.0.3. 

Customers can also protect against the attack by disabling CBC mode cipher 
suites on clients and servers. Cipher suites that use RC4 and, if TLS 1.2 is 
available, AES-GCM can be used. 



Obtaining Downloads

To request your upgrade of the software, please call your local support 
telephone number (contact phone numbers are available at 
http://www.rsa.com/node.aspx?id=1356 ) for most expedient service. You may also 
request your software upgrade online at http://www.rsa.com/go/form_ins.asp .



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.rsa.com/node.aspx?id=1264



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.rsa.com/node.aspx?id=2575 



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)

iEYEARECAAYFAlHBw08ACgkQtjd2rKp+ALyHQACggG2us3gMSQQX4Ol0+Zxrqjvi
QAsAoLKL5rrl9BDb54SQ0i7K57mGy9S/
=JcQv
-----END PGP SIGNATURE-----