Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [day] [month] [year] [list]
Date: Fri, 08 Oct 2010 17:07:02 +0200
From: Jan Lieskovsky <>
To: "Steven M. Christey" <>
CC: oss-security <>,
        Bill Janssen <>,
        Andreas Hasenack <>,
        Mads Kiilerich <>
Subject: CVE Request -- Mercurial --Doesn't verify subject Common Name properly

Hello Steve, vendors,

   a security flaw was found in the way Mercurial handled subject
Common Name field of the provided certificate (the check
if the commonName in the received certificate matches the
requested hostname was not performed). An attacker, able
to get a carefully-crafted certificate signed by a Certificate
Authority could use the certificate during a man-in-the-middle
attack and potentially confuse Mercurial into accepting it by

Upstream patch:

According to [1] the true reason for this problem is the new python SSL
module implementation:

and as stated in:

it should be decision made by application designers, if the subject CN
field will be checked despite of the python SSL module implementation.

So could you allocate a CVE identifier for this issue(s)?

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

Powered by blists - more mailing lists

Your e-mail address:

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.