Vulnerability Note VU#111034

GnuTLS Server Name extension Denial of Service

Original Release date: 29 May 2008 | Last revised: 29 May 2008


A vulnerability exists in GnuTLS that may allow a remote attacker to cause a denial of service.


GnuTLS contains a vulnerability in gnults-serv that may result in a denial of service when handling a specially crafted Client Hello message. According to CERT-FI Vulnerability Advisory on GnuTLS:

    The problem occurs when gnutls-serv receives Client Hello message which contains Server name extension where the length of the server name list is set to 18 and the data of the server name list consists of 18 zero octets. After receiving this Client Hello message gnutls-serv continues to function normally, but crashes after Finished messages when it tries to pack the session data in function pack_security_parameters() (in lib/gnutls_session_pack.c).

Note that this issue may affect GnuTLS versions prior to 2.2.5 and also affects version 2.3.0.


A remote, unauthorized attacker may be able to cause a denial of service.


Upgrade or Apply Patch
GnuTLS has issued an upgrade and a patch to address this issue. See GnuTLS Security Advisory SA-2008-01 for more information. GnuTLS is included in various Linux and UNIX distributions. Please consult the relevant documentation of your distribution to obtain the appropriate updates.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
GnuTLSAffected-29 May 2008
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



This issue was reported in GnuTLS Security Advisory SA-2008-01 . GnuTLS credits Ossi Herrala and Jukka Taimisto from the CROSS project at Codenomicon Ltd. for reporting this issue.

This document was written by Chris Taschner.

Other Information

  • CVE IDs: CVE-2008-1950
  • Date Public: 19 May 2008
  • Date First Published: 29 May 2008
  • Date Last Updated: 29 May 2008
  • Severity Metric: 9.19
  • Document Revision: 3


If you have feedback, comments, or additional information about this vulnerability, please send us email.