Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 09 Mar 2010 19:00:57 +0100
From: Jan Lieskovsky <>
To: "Steven M. Christey" <>, Kees Cook <>
CC: Brian Stafford <>,
        oss-security <>,,
Subject: Re: CVE Request: libesmtp does not check NULL bytes
 in commonName

Hi Steve,

Kees Cook wrote:
> Hello,
> I just noticed that libesmtp does not appear to handle NULL-byte CNs, as
> seen with the original browser-based issue:
> Related to this are failures in wildcard handling:
> and CN-specificity:
> Though it may be a non-issue if TLS doesn't function at all:

   any progress while assigning CVE ids for these issues?

   From what I can tell, two should be enough:
   a, libESMTP doesn't properly handle NULL character in Common Name

     References: (issue 2c)

   b, libESMTP's match_component() accepts two strings as equal
      if they start equal but don't have equal length => cert forgery


   Kees, please correct me, if I omitted something.

Thanks && Regards, Jan.
Jan iankko Lieskovsky / Red Hat Security Response Team

> -Kees

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.