What is the severity of CVE-2014-0626?

CVE-2014-0626 has a high severity rating due to its potential to allow remote attackers to bypass cryptographic protections.

How do I fix CVE-2014-0626?

To fix CVE-2014-0626, upgrade to EMC RSA BSAFE SSL-J version 5.1.3 or later, or version 6.0.2 or later.

Which versions of EMC RSA BSAFE SSL-J are affected by CVE-2014-0626?

Affected versions of EMC RSA BSAFE SSL-J include 5.0, 5.1.0, 5.1.1, 5.1.2, 6.0, and 6.0.1.

What type of attack is CVE-2014-0626 vulnerable to?

CVE-2014-0626 is vulnerable to cryptographic protection bypass attacks during the TLS handshake.

Is there a workaround for CVE-2014-0626 if I cannot immediately upgrade?

There is no official workaround for CVE-2014-0626, so upgrading to fixed versions is strongly recommended.

Vulnerability/
CVE-2014-0626

medium

CWE

310

18/2/2014

6/8/2024

CVE-2014-0626

First published: Tue Feb 18 2014(Updated: )

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 unauthenticated.

Credit: security_alert@emc.com

Affected Software	Affected Version	How to fix
EMC RSA BSAFE SSL-J	=5.1.2
EMC RSA BSAFE SSL-J	=6.0
EMC RSA BSAFE Toolkits	=5.0
EMC RSA BSAFE Toolkits	=5.1.0
EMC RSA BSAFE Toolkits	=5.1.1
EMC RSA BSAFE Toolkits	=6.0.1

Never miss a vulnerability like this again

Reference Links

http://archives.neohapsis.com/archives/bugtraq/2014-02/0061.html

Frequently Asked Questions

What is the severity of CVE-2014-0626?
CVE-2014-0626 has a high severity rating due to its potential to allow remote attackers to bypass cryptographic protections.
How do I fix CVE-2014-0626?
To fix CVE-2014-0626, upgrade to EMC RSA BSAFE SSL-J version 5.1.3 or later, or version 6.0.2 or later.
Which versions of EMC RSA BSAFE SSL-J are affected by CVE-2014-0626?
Affected versions of EMC RSA BSAFE SSL-J include 5.0, 5.1.0, 5.1.1, 5.1.2, 6.0, and 6.0.1.
What type of attack is CVE-2014-0626 vulnerable to?
CVE-2014-0626 is vulnerable to cryptographic protection bypass attacks during the TLS handshake.
Is there a workaround for CVE-2014-0626 if I cannot immediately upgrade?
There is no official workaround for CVE-2014-0626, so upgrading to fixed versions is strongly recommended.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/references
agent/weakness
agent/severity
agent/last-modified-date
agent/event
agent/first-publish-date
agent/description
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/dell
canonical/emc rsa bsafe ssl-j
version/emc rsa bsafe ssl-j/5.1.2
version/emc rsa bsafe ssl-j/6.0
vendor/emc
canonical/emc rsa bsafe toolkits
version/emc rsa bsafe toolkits/5.0
version/emc rsa bsafe toolkits/5.1.0
version/emc rsa bsafe toolkits/5.1.1
version/emc rsa bsafe toolkits/6.0.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.