[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ESA-2014-009: RSA BSAFE® SSL-J Multiple Vulnerabilities
- To: "bugtraq@xxxxxxxxxxxxxxxxx" <bugtraq@xxxxxxxxxxxxxxxxx>, "dm@xxxxxxxxxxxxxxxxx" <dm@xxxxxxxxxxxxxxxxx>
- Subject: ESA-2014-009: RSA BSAFE® SSL-J Multiple Vulnerabilities
- From: Security Alert <Security_Alert@xxxxxxx>
- Date: Fri, 14 Feb 2014 14:29:44 +0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ESA-2014-009: RSA BSAFE® SSL-J Multiple Vulnerabilities
EMC Identifier: ESA-2014-009
CVE Identifier: CVE-2011-1473, CVE-2014-0625, CVE-2014-0626, CVE-2014-0627
Severity Rating: CVSS v2 Base Score: See below for individual scores
Affected Products:
All versions of RSA BSAFE SSL-J (SSL-J) 5.x, SSL-J 6.0
Unaffected Products:
SSL-J 5.1.3, 6.0.2 and 6.1.x
Summary:
SSL-J 6.1.x, 6.0.2 and 5.1.3 contain updates designed to prevent multiple
potential security vulnerabilities.
Addressed issues include:
1. SSL/TLS Renegotiation Denial of Service Vulnerability (CVE-2011-1473)
2. SSLEngine API Information Disclosure Vulnerability (CVE-2014-0627)
3. SSL-J JSAFE and JSSE API Information Disclosure Vulnerability
(CVE-2014-0626)
4. SSLSocket Denial of Service Vulnerability (CVE-2014-0625)
Details:
SSL/TLS Renegotiation Denial of Service Vulnerability (CVE-2011-1473)
An application that does not properly restrict client-initiated renegotiation
within the SSL and TLS protocols could be vulnerable to a denial of service
(CPU consumption) from remote attackers that perform many renegotiations within
a single connection. See
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-1473 for more
information.
SSL-J 6.1.x, 6.0.2 and 5.1.3 are designed to include a patch to determine the
number of renegotiations that have been initiated by each SSL/TLS client for
each connection, and to help ensure that the server can set a limit on
renegotiation requests.
CVSS v2 Base Score:5.0 (AV:N/AC:L/Au:N/C:N/I:N/A:P)
SSLEngine API Information Disclosure Vulnerability (CVE-2014-0627)
When the SSL-J implementation of the SSLEngine API is used, it is possible for
Application Data to be sent using the ?wrap? method, after sending the Finished
message. However at this time, when the initial handshake is either an
abbreviated handshake in server mode or a full handshake in client mode, the
handshake is incomplete because the peer?s Finished message has not been
received. This can occur for both the TLS client and server.
The Application Data that is sent in this manner could be vulnerable to an
attacker forcing the use of a weak cipher suite (if weak cipher suites are
enabled).
CVSS v2 Base Score: 4.0 (AV:N/AC:H/Au:N/C:P/I:P/A:N)
SSL-J JSAFE and JSSE API Information Disclosure Vulnerability (CVE-2014-0626)
Unencrypted and unauthenticated Application Data can be received by the client
or server during the TLS handshake. This Application Data is indistinguishable
from data received after the completion of the handshake. This applies to the
SSL-J JSAFE and JSSE APIs.
CVSS v2 Base Score: 4.0 (AV:N/AC:H/Au:N/C:P/I:P/A:N)
SSLSocket Denial of Service Vulnerability (CVE-2014-0625)
If SSLSocket (from both the JSAFE and JSSE APIs) is used, Application Data that
is received while a handshake is in progress is placed in an internal buffer.
This buffer can grow and use up large amounts of memory.
CVSS v2 Base Score: 4.3 (AV:N/AC:M/Au:N/C:N/I:N/A:P)
Recommendation:
RSA recommends that customers on SSL-J 5.1.x or lower upgrade to SSL-J 5.1.3,
6.0.2 or 6.1.1.
RSA recommends that customers on SSL-J 6.0 upgrade to SSL-J 6.0.2 or 6.1.1.
The patch to address CVE-2011-1473 is only applicable on the server side.
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/phone-numbers.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)
iEYEARECAAYFAlL+J8kACgkQtjd2rKp+ALx9YACdGPsy/gb0z9h5Dpz7vRtn19Gg
iboAn2FBLI5QgwQNSzHY3t0Abc38c3tp
=DDww
-----END PGP SIGNATURE-----