CVE-2014-2900: Medium severity yaSSL CyaSSL vulnerability

Published Apr 22, 2014
·
Updated

wolfSSL CyaSSL before 2.9.4 does not properly validate X.509 certificates with unknown critical extensions, which allows man-in-the-middle attackers to spoof servers via crafted X.509 certificate.

Affected Software

45 affected components
yaSSL CyaSSL<=2.9.0
yaSSL CyaSSL=0.2.0
yaSSL CyaSSL=0.3.0
yaSSL CyaSSL=0.4.0
yaSSL CyaSSL=0.5.0
yaSSL CyaSSL=0.5.5
yaSSL CyaSSL=0.6.0
yaSSL CyaSSL=0.6.2
yaSSL CyaSSL=0.6.3
yaSSL CyaSSL=0.8.0
yaSSL CyaSSL=0.9.0
yaSSL CyaSSL=0.9.6
yaSSL CyaSSL=0.9.8
yaSSL CyaSSL=0.9.9
yaSSL CyaSSL=1.0.0-rc1
yaSSL CyaSSL=1.0.0-rc2
yaSSL CyaSSL=1.0.0-rc3
yaSSL CyaSSL=1.0.2
yaSSL CyaSSL=1.0.3
yaSSL CyaSSL=1.0.6
yaSSL CyaSSL=1.1.0
yaSSL CyaSSL=1.2.0
yaSSL CyaSSL=1.3.0
yaSSL CyaSSL=1.4.0
yaSSL CyaSSL=1.5.0
yaSSL CyaSSL=1.5.4
yaSSL CyaSSL=1.5.6
yaSSL CyaSSL=1.6.0
yaSSL CyaSSL=1.6.5
yaSSL CyaSSL=1.8.0
yaSSL CyaSSL=1.9.0
yaSSL CyaSSL=2.0.0-rc1
yaSSL CyaSSL=2.0.0-rc2
yaSSL CyaSSL=2.0.0-rc3
yaSSL CyaSSL=2.0.2
yaSSL CyaSSL=2.0.6
yaSSL CyaSSL=2.0.8
yaSSL CyaSSL=2.2.0
yaSSL CyaSSL=2.3.0
yaSSL CyaSSL=2.4.0
yaSSL CyaSSL=2.4.6
yaSSL CyaSSL=2.5.0
yaSSL CyaSSL=2.6.0
yaSSL CyaSSL=2.7.0
yaSSL CyaSSL=2.8.0

Event History

Apr 22, 2014
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:23 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What vulnerabilities are associated with CVE-2014-2900?

CVE-2014-2900 allows man-in-the-middle attackers to spoof servers via crafted X.509 certificates due to improper validation of unknown critical extensions.

2

Which versions of CyaSSL are affected by CVE-2014-2900?

CVE-2014-2900 affects all versions of CyaSSL before 2.9.4.

3

How can I mitigate the issues related to CVE-2014-2900?

To mitigate CVE-2014-2900, upgrade CyaSSL to version 2.9.4 or later, which fixes the improper certificate validation issue.

4

Is CVE-2014-2900 a high severity vulnerability?

Yes, CVE-2014-2900 is considered to have a high severity due to its potential for exploitation in man-in-the-middle attacks.

5

What should I do if I cannot upgrade to fix CVE-2014-2900?

If you are unable to upgrade, consider implementing additional network security measures such as using VPNs or other protocols to protect against man-in-the-middle attacks.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203