CVE-2015-6251: Use After Free
A use-after-free flaw was found in GnuTLS's gnutlsx509dntostring() function. A remote attacker could create a specially crafted certificate with very long DistinguishedName (DN) entries that, when processed by an application compiled against GnuTLS, could cause that application to crash.
This issue was fixed in upstream versions 3.4.4 and 3.3.17 of GnuTLS:
https://lists.gnupg.org/pipermail/gnutls-devel/2015-August/007707.html https://lists.gnupg.org/pipermail/gnutls-devel/2015-August/007708.html
The following patch fixes this issue:
https://gitlab.com/gnutls/gnutls/commit/272854367efc130fbd4f1a51840d80c630214e12
The affected function, gnutlsx509dntostring(), was first introduced in version 3.1.10 via commit:
https://gitlab.com/gnutls/gnutls/commit/6be35136333b5d6289f23209cf896e741462909a
The gnutls packages in Red Hat Enterprise Linux 6 and earlier include GnuTLS versions 2.x or 1.x and are therefore not affected by this issue.
External References:
http://www.gnutls.org/security.html#GNUTLS-SA-2015-3
Other sources
Double free vulnerability in GnuTLS before 3.3.17 and 3.4.x before 3.4.4 allows remote attackers to cause a denial of service via a long DistinguishedName (DN) entry in a certificate.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2015-6251?
CVE-2015-6251 has a medium severity rating, as it can lead to a denial of service by crashing the application.
How do I fix CVE-2015-6251?
To fix CVE-2015-6251, upgrade GnuTLS to version 3.4.4 or later, or version 3.3.17 or later.
Which versions of GnuTLS are affected by CVE-2015-6251?
CVE-2015-6251 affects GnuTLS versions prior to 3.4.4 and 3.3.17.
What can an attacker do with CVE-2015-6251?
An attacker can exploit CVE-2015-6251 by sending a specially crafted certificate to an application using GnuTLS, causing it to crash.
How can I determine if my application is vulnerable to CVE-2015-6251?
Check the version of GnuTLS linked to your application; if it's older than 3.4.4 or 3.3.17, it is vulnerable to CVE-2015-6251.