Re: CVE Request -- urllib3: Does not check for SSL certificates by default

[Jan Lieskovsky <jlieskov () redhat com>]

Steve,

  in relation to this one the following question has been
raised internally - it's OK to assign CVE identifier for
end user applications, proclaiming to perform SSL certificates
verification, but not doing that.

  But what about the libraries? Obviously urllib3 when instructed
to do so, performs the verification. The question is should it
get a CVE identifier or not? Could you clarify Mitre's opinion /
view on this?

Thank you && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Response Team

> Hello Kurt, Steve, vendors,
>
>   it was reported that urllib3, a Python HTTP library
> with thread-safe connection pooling and file post support,
> did not perform SSL certificates verification by default.
> A rogue HTTP server could use this flaw to conduct
> man-in-the-middle (MITM) attacks.
>
> References:
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686872
> [2] https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1047054
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=855320
>     (the bug actually has python-requests in the summary,
>      but only due the fact it contains embedded urllib3)
>
> Patch applied by the Ubuntu Linux distribution:
> [4] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=python-urllib3_1.3-2ubuntu1.debdiff;att=1;bug=686872
>
> Reproducer:
> [5] https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1047054/comments/0
>
> Could you allocate a CVE id for this?
>
> Thank you && Regards, Jan.
> --
> Jan iankko Lieskovsky / Red Hat Security Response Team