From owner-svn-ports-all@FreeBSD.ORG Wed Jun 17 21:40:52 2015 Return-Path: Delivered-To: svn-ports-all@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D327D9E; Wed, 17 Jun 2015 21:40:52 +0000 (UTC) (envelope-from delphij@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C05E58A4; Wed, 17 Jun 2015 21:40:52 +0000 (UTC) (envelope-from delphij@FreeBSD.org) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t5HLeqMO048754; Wed, 17 Jun 2015 21:40:52 GMT (envelope-from delphij@FreeBSD.org) Received: (from delphij@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t5HLeqUS048753; Wed, 17 Jun 2015 21:40:52 GMT (envelope-from delphij@FreeBSD.org) Message-Id: <201506172140.t5HLeqUS048753@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: delphij set sender to delphij@FreeBSD.org using -f From: Xin LI Date: Wed, 17 Jun 2015 21:40:52 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r389995 - head/security/vuxml X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 21:40:53 -0000 Author: delphij Date: Wed Jun 17 21:40:51 2015 New Revision: 389995 URL: https://svnweb.freebsd.org/changeset/ports/389995 Log: Document two vulnerabilities of cURL. Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Wed Jun 17 20:16:43 2015 (r389994) +++ head/security/vuxml/vuln.xml Wed Jun 17 21:40:51 2015 (r389995) @@ -57,6 +57,77 @@ Notes: --> + + cURL -- Multiple Vulnerability + + + curl + 7.407.43 + + + + +

cURL reports:

+
libcurl can wrongly send HTTP credentials when re-using + connections.
+
libcurl allows applications to set credentials for the + upcoming transfer with HTTP Basic authentication, like + with CURLOPT_USERPWD for example. Name and password. + Just like all other libcurl options the credentials + are sticky and are kept associated with the "handle" + until something is made to change the situation.
+
Further, libcurl offers a curl_easy_reset() function + that resets a handle back to its pristine state in + terms of all settable options. A reset is of course + also supposed to clear the credentials. A reset is + typically used to clear up the handle and prepare + it for a new, possibly unrelated, transfer.
+
Within such a handle, libcurl can also store a + set of previous connections in case a second transfer + is requested to a host name for which an existing + connection is already kept alive.
+
With this flaw present, using the handle even + after a reset would make libcurl accidentally use + those credentials in a subseqent request if done + to the same host name and connection as was + previously accessed.
+
An example case would be first requesting a password + protected resource from one section of a web site, and + then do a second request of a public resource from a + completely different part of the site without + authentication. This flaw would then inadvertently + leak the credentials in the second request.
+

+
libcurl can get tricked by a malicious SMB server to + send off data it did not intend to.
+
In libcurl's state machine function handling the SMB + protocol (smb_request_state()), two length and offset + values are extracted from data that has arrived over + the network, and those values are subsequently used + to figure out what data range to send back.
+
The values are used and trusted without boundary + checks and are just assumed to be valid. This allows + carefully handicrafted packages to trick libcurl + into responding and sending off data that was not + intended. Or just crash if the values cause libcurl + to access invalid memory.
+

+ + + + CVE-2015-3236 + CVE-2015-3237 + http://curl.haxx.se/docs/adv_20150617A.html + http://curl.haxx.se/docs/adv_20150617B.html + + + 2015-06-17 + 2015-06-17 + + + rubygem-rails -- multiple vulnerabilities