From owner-svn-ports-all@freebsd.org Wed May 16 23:56:08 2018 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80F3CEDE97F; Wed, 16 May 2018 23:56:08 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01B5784A95; Wed, 16 May 2018 23:56:06 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7C60F2128B; Wed, 16 May 2018 23:56:06 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w4GNu6IY019549; Wed, 16 May 2018 23:56:06 GMT (envelope-from sunpoet@FreeBSD.org) Received: (from sunpoet@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w4GNu6AV019548; Wed, 16 May 2018 23:56:06 GMT (envelope-from sunpoet@FreeBSD.org) Message-Id: <201805162356.w4GNu6AV019548@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: sunpoet set sender to sunpoet@FreeBSD.org using -f From: Sunpoet Po-Chuan Hsieh Date: Wed, 16 May 2018 23:56:06 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r470180 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: sunpoet X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 470180 X-SVN-Commit-Repository: ports 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.26 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, 16 May 2018 23:56:08 -0000 Author: sunpoet Date: Wed May 16 23:56:05 2018 New Revision: 470180 URL: https://svnweb.freebsd.org/changeset/ports/470180 Log: Document curl vulnerability Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Wed May 16 23:55:59 2018 (r470179) +++ head/security/vuxml/vuln.xml Wed May 16 23:56:05 2018 (r470180) @@ -58,6 +58,64 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + cURL -- multiple vulnerabilities + + + curl + 7.60.0 + + + + +

cURL security problems:

+
CVE-2018-1000300: FTP shutdown response buffer overflow
+
curl might overflow a heap based memory buffer when closing down an + FTP connection with very long server command replies.
+
When doing FTP transfers, curl keeps a spare "closure handle" around + internally that will be used when an FTP connection gets shut down + since the original curl easy handle is then already removed.
+
FTP server response data that gets cached from the original transfer + might then be larger than the default buffer size (16 KB) allocated in + the "closure handle", which can lead to a buffer overwrite. The + contents and size of that overwrite is controllable by the server.
+
This situation was detected by an assert() in the code, but that was + of course only preventing bad stuff in debug builds. This bug is very + unlikely to trigger with non-malicious servers.
+
We are not aware of any exploit of this flaw.
+
CVE-2018-1000301: RTSP bad headers buffer over-read
+
curl can be tricked into reading data beyond the end of a heap based + buffer used to store downloaded content.
+
When servers send RTSP responses back to curl, the data starts out + with a set of headers. curl parses that data to separate it into a + number of headers to deal with those appropriately and to find the end + of the headers that signal the start of the "body" part.
+
The function that splits up the response into headers is called + Curl_http_readwrite_headers() and in situations where it can't find a + single header in the buffer, it might end up leaving a pointer pointing + into the buffer instead of to the start of the buffer which then later + on may lead to an out of buffer read when code assumes that pointer + points to a full buffer size worth of memory to use.
+
This could potentially lead to information leakage but most likely a + crash/denial of service for applications if a server triggers this flaw.
+
We are not aware of any exploit of this flaw.
+

+ + + + https://curl.haxx.se/docs/security.html + https://curl.haxx.se/docs/adv_2018-82c2.html + https://curl.haxx.se/docs/adv_2018-b138.html + CVE-2018-1000300 + CVE-2018-1000301 + + + 2018-05-16 + 2018-05-16 + + + wavpack -- multiple vulnerabilities