Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2015.0010
ESA-2014-158: RSA BSAFE Micro Edition Suite and SSL-J Triple
Handshake Vulnerability
5 January 2015
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: RSA BSAFE Micro Edition Suite
RSA BSAFE SSL-J
Publisher: EMC
Operating System: Windows
Solaris
Red Hat
HP-UX
Impact/Access: Execute Arbitrary Code/Commands -- Remote with User Interaction
Access Privileged Data -- Remote with User Interaction
Provide Misleading Information -- Remote with User Interaction
Resolution: Patch/Upgrade
CVE Names: CVE-2014-4630
- --------------------------BEGIN INCLUDED TEXT--------------------
ESA-2014-158: RSA BSAFE Micro Edition Suite and SSL-J 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
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)
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.
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.
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
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBVKn88hLndAQH1ShLAQK4pA//SHbd5DiWWSbMBFLbEYT1Dl6vz+hs89G/
vHYd6NxXhwUBDCDuN+CzpOrAZ426IVVGLnCmSYKL6Co6aa1BOKVP/XJu98NJHewm
1VrripMa/sWNqnRK2TQk/sORPn9VLVYtkTpW5Bo/4Q1GZnGG1dIkOB/G3DQgL7l5
1Ik5/B5DCUKoeFp4k/Y+UJXDsQcv5oBEZ3dK+y2lJijJLC97AhJ0yJ0sPex5ipdG
hVwTH44RqLiG5zq/XI+YHKBeSSinraV+sBjCPZIsXsrojJ7anTizFrIooUqS42rH
GQtURSnj9kU03nAsTXFL5VkM4dOo5CAyiE+7oSPj0qAsT2+byBCG2lEfbTx8J7kY
dOti/z6olopPytjRDH1TfsAt5h8K93xXsbNK55rIXappqeELM6FRqtXnIfNZP83Q
oUTFCrHx2ZKkxKvkWC9C9A2/0YfDX+Jn6ARR+R20Y8pODM8GadyYQ3autXfktBiR
TmCVdTs+V/6qENEHYa+gg68xmitFPtVZc83Ph39B6mWJo1DquNB59Qnce6L8iDLs
frtk31zJYOQuLwIct0S3zm9NMt1WuLFpcyfBhWxu9IvReLnfwmnOYpFDMLXIGgqq
f0aD9H5RvUmIROdzcrmpEfwoFz/edpDsy1hcjjV2CIYtU6HkFAajeqoFTrleMwYx
RiFezgDrlkM=
=2VuH
-----END PGP SIGNATURE-----