From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: [PATCH 0/1] curl: Fix CVE-2016-3739. Date: Sat, 11 Jun 2016 23:38:29 -0400 Message-ID: Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55123) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bBwEh-0000ZJ-Am for guix-devel@gnu.org; Sat, 11 Jun 2016 23:38:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bBwEa-0004uq-MC for guix-devel@gnu.org; Sat, 11 Jun 2016 23:38:54 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:56217) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bBwEY-0004re-Cx for guix-devel@gnu.org; Sat, 11 Jun 2016 23:38:48 -0400 Received: from localhost.localdomain (unknown [65.210.89.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 8EB96F2022 for ; Sat, 11 Jun 2016 23:38:35 -0400 (EDT) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org If your SSL / TLS provider is mbedTLS (formerly PolarSSL), there is a bug in curl [CVE-2016-3739] that allows an attacker to bypass the full certificate check by presenting any valid certificate. So, you might think are connecting to https://example.com, when in fact the attacker has a certificate for any other domain. We don't package mbedTLS, but I still think we should provide the fixed source code. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3739 https://curl.haxx.se/docs/adv_20160518.html Leo Famulari (1): gnu: curl: Replace with 7.49.1 [fixes CVE-2016-3739]. gnu/packages/curl.scm | 15 +++++++++++++++ 1 file changed, 15 insertions(+) -- 2.8.4