CWE
310
Advisory Published
CVE Published
Updated

CVE-2014-0092

First published: Tue Feb 25 2014(Updated: )

It was discovered that GnuTLS X.509 certificate verification code failed to properly handle certain errors that can occur during the certificate verification. When such errors are encountered, GnuTLS would report successful verification of the certificate, even though verification should end with failure. A specially-crafted certificate can be accepted by GnuTLS as valid even if it wasn't issued by any trusted Certificate Authority. This can be used to perform man-in-the-middle attacks against applications using GnuTLS.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/gnutls<3.1.22
3.1.22
redhat/gnutls<3.2.12
3.2.12
GnuTLS<=3.2.11
GnuTLS=3.2.0
GnuTLS=3.2.1
GnuTLS=3.2.2
GnuTLS=3.2.3
GnuTLS=3.2.4
GnuTLS=3.2.5
GnuTLS=3.2.6
GnuTLS=3.2.7
GnuTLS=3.2.8
GnuTLS=3.2.8.1
GnuTLS=3.2.9
GnuTLS=3.2.10
GnuTLS<=3.1.21
GnuTLS=3.1.0
GnuTLS=3.1.1
GnuTLS=3.1.2
GnuTLS=3.1.3
GnuTLS=3.1.4
GnuTLS=3.1.5
GnuTLS=3.1.6
GnuTLS=3.1.7
GnuTLS=3.1.8
GnuTLS=3.1.9
GnuTLS=3.1.10
GnuTLS=3.1.11
GnuTLS=3.1.12
GnuTLS=3.1.13
GnuTLS=3.1.14
GnuTLS=3.1.15
GnuTLS=3.1.16
GnuTLS=3.1.17
GnuTLS=3.1.18
GnuTLS=3.1.19
GnuTLS=3.1.20

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2014-0092?

    CVE-2014-0092 is rated as a high severity vulnerability due to improper handling of errors during X.509 certificate verification in GnuTLS.

  • How do I fix CVE-2014-0092?

    To fix CVE-2014-0092, upgrade GnuTLS to version 3.1.22 or later for the 3.1.x branch, or version 3.2.12 or later for the 3.2.x branch.

  • Which versions of GnuTLS are affected by CVE-2014-0092?

    GnuTLS versions up to and including 3.1.21 and 3.2.11 are affected by CVE-2014-0092.

  • What could happen if CVE-2014-0092 is exploited?

    Exploiting CVE-2014-0092 could allow an attacker to successfully verify a fraudulent certificate, compromising secure communications.

  • Is there a workaround for CVE-2014-0092?

    There are no specific workarounds for CVE-2014-0092, so updating to a fixed version is strongly recommended.

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