Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 23 Dec 2010 19:55:50 +0100
From: Nicolas Sebrecht <>
To: Jan Lieskovsky <>
Cc: "Steven M. Christey" <>,
	oss-security <>,
	Nicolas Sebrecht <>,
	david b <>, Johannes Stezenbach <>,
	Christoph Höger <>,
	John Goerzen <>
Subject: Re: CVE Request -- OfflineIMAP -- 1), failed to validate remote
 SSL server certificate 2), allows SSLv2 protocol

On Thu, Dec 23, 2010 at 03:43:40PM +0100, Jan Lieskovsky wrote:
>   I), Didn't check SSL server certificate
>   Description:
>   OfflineIMAP prior commit:
>   [1]
>   did not perform SSL server certificate validation,
>   even when "ssl = yes" option was specified in the
>   configuration file. If an attacker was able to get
>   a carefully-crafted certificate signed by a
>   Certificate Authority trusted by OfflineIMAP,
>   the attacker could use the certificate during a
>   man-in-the-middle attack and potentially confuse
>   OfflineIMAP into accepting it by mistake.
>   References:
>   [2]
>   [3]

First of all, thank you very much Jan and all the Redhat team for
reporting it up to the CVE database.

The given patch from Sebastian Spaeth has been released in v6.3.2-rc1. I
encourage distribution maintainers who want this fix to either

  deploy the RC release as is


  backport the fix against the last release they own.

I expect to release a new stable soon but I still didn't have feedback
from users using SSL. The lack of feedback could mean that

  OfflineIMAP users don't expect SSL to work by still refering to the
  documentation they know (stating that SSL checks is not supported)


  they don't hit problems at all.

So, I'll wait a bit more before releasing the next stable.

>   II), Allows SSLv2 protocol
>   Description:
>   In commit:
>   [4]
>   when SSL server certificate validation support was added
>   to OfflineIMAP it was still possible to use SSL v2 protocol
>   version. Version 2 of SSL protocol version is known
>   to be prone to multiple deficiencies, each of them
>   having security implications (to mention some of them):
>   [5]
>   Thus SSLv2 protocol version should be disabled in OfflineIMAP.
>   References:
>   [6]
>   [7]


> Could you allocate CVE ids for these issues? (though opened for
> discussion of any / none of them worthy of it)

As the maintainer of OfflineIMAP, I think both issues should have their
entry in the CVE List.

Let us know if you want more clarifications.


Nicolas Sebrecht

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.