CVE-2014-3465: Null Pointer Dereference

Published May 27, 2014
·
Updated

A NULL pointer dereference flaw was discovered in GnuTLS's gnutlsx509dnoidname(). The function, when called with the GNUTLSX509DNOIDRETURNOID flag, should not return NULL to its caller. However, it could previously return NULL when parsed X.509 certificates included specific OIDs.

The issue was corrected upstream using the following commit: https://www.gitorious.org/gnutls/gnutls/commit/d3648ebb04b650e6d20a2ec1fb839256b30b9fc6

The fix was first included in upstream versions 3.1.20 and 3.2.10: http://thread.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/7251 http://thread.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/7250

Affected function was introduced in GnuTLS version 3.0: http://gnutls.org/manual/htmlnode/X509-certificate-API.html#gnutls005fx509005fdn005foid005fname-1

The gnutls packages in Red Hat Enterprise Linux 6 and earlier include GnuTLS versions 2.x or 1.x and were therefore not affected by this issue. The gnutls and mingw-gnutls packages in Fedora are already updated to the fixed upstream version.

Other sources

The gnutlsx509dnoidname function in lib/x509/common.c in GnuTLS 3.0 before 3.1.20 and 3.2.x before 3.2.10 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted X.509 certificate, related to a missing LDAP description for an OID when printing the DN.

MITRE

Affected Software

62 affected componentsFixes available
redhat/gnutls<3.1.20
3.1.20
redhat/gnutls<3.2.10
3.2.10
GNU GnuTLS=3.0.0
GNU GnuTLS=3.0.1
GNU GnuTLS=3.0.2
GNU GnuTLS=3.0.3
GNU GnuTLS=3.0.4
GNU GnuTLS=3.0.5
GNU GnuTLS=3.0.6
GNU GnuTLS=3.0.7
GNU GnuTLS=3.0.8
GNU GnuTLS=3.0.9
GNU GnuTLS=3.0.10
GNU GnuTLS=3.0.11
GNU GnuTLS=3.0.12
GNU GnuTLS=3.0.13
GNU GnuTLS=3.0.14
GNU GnuTLS=3.0.15
GNU GnuTLS=3.0.16
GNU GnuTLS=3.0.17
GNU GnuTLS=3.0.18
GNU GnuTLS=3.0.19
GNU GnuTLS=3.0.20
GNU GnuTLS=3.0.21
GNU GnuTLS=3.0.22
GNU GnuTLS=3.0.23
GNU GnuTLS=3.0.24
GNU GnuTLS=3.0.25
GNU GnuTLS=3.0.26
GNU GnuTLS=3.0.27
GNU GnuTLS=3.0.28
GNU GnuTLS=3.1.0
GNU GnuTLS=3.1.1
GNU GnuTLS=3.1.2
GNU GnuTLS=3.1.3
GNU GnuTLS=3.1.4
GNU GnuTLS=3.1.5
GNU GnuTLS=3.1.6
GNU GnuTLS=3.1.7
GNU GnuTLS=3.1.8
GNU GnuTLS=3.1.9
GNU GnuTLS=3.1.10
GNU GnuTLS=3.1.11
GNU GnuTLS=3.1.12
GNU GnuTLS=3.1.13
GNU GnuTLS=3.1.14
GNU GnuTLS=3.1.15
GNU GnuTLS=3.1.16
GNU GnuTLS=3.1.17
GNU GnuTLS=3.1.18
GNU GnuTLS=3.1.19
GNU GnuTLS=3.2.0
GNU GnuTLS=3.2.1
GNU GnuTLS=3.2.2
GNU GnuTLS=3.2.3
GNU GnuTLS=3.2.4
GNU GnuTLS=3.2.5
GNU GnuTLS=3.2.6
GNU GnuTLS=3.2.7
GNU GnuTLS=3.2.8
GNU GnuTLS=3.2.8.1
GNU GnuTLS=3.2.9

Event History

Jun 10, 2014
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:55 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2014-3465?

CVE-2014-3465 is classified as a medium severity vulnerability due to the potential for a NULL pointer dereference.

2

How do I fix CVE-2014-3465?

To fix CVE-2014-3465, upgrade to GnuTLS versions 3.1.20 or 3.2.10 or later.

3

Which versions of GnuTLS are affected by CVE-2014-3465?

CVE-2014-3465 affects GnuTLS versions prior to 3.1.20 and 3.2.10.

4

What are the implications of the vulnerability CVE-2014-3465?

The implications of CVE-2014-3465 include potential crashes or unexpected behavior in applications using GnuTLS when handling certain X.509 certificates.

5

Who discovered CVE-2014-3465?

CVE-2014-3465 was reported by the GnuTLS development community.

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