ESA-2014-009: RSA BSAFE® SSL-J Multiple Vulnerabilities

ESA-2014-009.txt -----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...

ESA-2013-039: RSA BSAFE® SSL-J Multiple Vulnerabilities

ESA-2013-039.txt -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ESA-2013-039: RSA BSAFE® SSL-J Multiple Vulnerabilities EMC Identifier: ESA-2013-039 CVE Identifier: CVE-2011-3389, CVE-2013-0169 Severity Rating: CVSS v2 Base Score: Refer NVD http://nvd.nist.gov/ for individual scores for each CVE...

CVE-2014-0626

The 1 JSAFE and 2 JSSE APIs in EMC RSA BSAFE SSL-J 5.x before 5.1.3 and 6.x before 6.0.2 make it easier for remote attackers to bypass intended cryptographic protection mechanisms by triggering application-data processing during the TLS handshake, a time at which the data is both unencrypted and...

CVE-2014-0627

The SSLEngine API implementation in EMC RSA BSAFE SSL-J 5.x before 5.1.3 and 6.x before 6.0.2 allows remote attackers to trigger the selection of a weak cipher suite by using the wrap method during a certain incomplete-handshake state...

Design/Logic Flaw

The 1 JSAFE and 2 JSSE APIs in EMC RSA BSAFE SSL-J 5.x before 5.1.3 and 6.x before 6.0.2 make it easier for remote attackers to bypass intended cryptographic protection mechanisms by triggering application-data processing during the TLS handshake, a time at which the data is both unencrypted and...

CVE-2014-0625

The CVE-2014-0625 issue affects RSA BSAFE SSL-J (JSAFE/JSSE) 5.x before 5.1.3 and 6.x before 6.0.2, where SSLSocket processing during TLS handshakes can buffer application data, leading to memory-based DoS. The SUSE/Security advisory and ESA-2014-009 describe a memory-denial vulnerability in the ...

CVE-2014-0627

Summary: CVE-2014-0627 affects EMC RSA BSAFE SSL-J (SSL-J) 5.x before 5.1.3 and 6.x before 6.0.2. The SSLEngine API can reveal information by using the wrap method after the Finished message in an incomplete handshake, potentially allowing an attacker to trigger a weak cipher suite. Impact: Infor...

CVE-2014-0626

The RSA BSAFE SSL-J vulnerability CVE-2014-0626 affects SSL-J 5.x (before 5.1.3) and 6.x (before 6.0.2). The JSAFE and JSSE APIs can process application data during the TLS handshake, exposing data unencrypted and unauthenticated and enabling potential information disclosure at handshake time. Ac...

ESA-2013-039: RSA BSAFE® SSL-J Multiple Vulnerabilities

ESA-2013-039.txt -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ESA-2013-039: RSA BSAFE® SSL-J Multiple Vulnerabilities EMC Identifier: ESA-2013-039 CVE Identifier: CVE-2011-3389, CVE-2013-0169 Severity Rating: CVSS v2 Base Score: Refer NVD http://nvd.nist.gov/ for individual scores for each CVE...

CVE-2001-1105

RSA BSAFE SSL-J 3.0, 3.0.1 and 3.1, as used in Cisco iCND 2.0, caches session IDs from failed login attempts, which could allow remote attackers to bypass SSL client authentication and gain access to sensitive data by logging in after an initial failure...

CVE-2001-1105

The CVE-2001-1105 entry affects RSA BSAFE SSL-J 3.0, 3.0.1 and 3.1 as used in Cisco iCND 2.0. The vulnerability is that the product caches session IDs from failed login attempts, which could allow remote attackers to bypass SSL client authentication and access sensitive data after an initial fail...

Cisco Security Advisory: Vulnerable SSL implementation in iCDN

-----BEGIN PGP SIGNED MESSAGE----- Cisco Security Advisory: Vulnerable SSL implementation in iCDN Revision 1.0 For public release 2001 September 12 08:00 GMT -0800 Summary A security vulnerability has been discovered in version 3.x of the RSA BSAFE SSL-J Software Developer Kit made by RSA Securit...

CVE-2001-1105

RSA BSAFE SSL-J 3.0, 3.0.1 and 3.1, as used in Cisco iCND 2.0, caches session IDs from failed login attempts, which could allow remote attackers to bypass SSL client authentication and gain access to sensitive data by logging in after an initial failure...