From owner-svn-ports-all@freebsd.org Thu Nov 1 19:20:07 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 B961E10D2E48; Thu, 1 Nov 2018 19:20:07 +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 6B28B88AA9; Thu, 1 Nov 2018 19:20:07 +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 2FE8E1FF9A; Thu, 1 Nov 2018 19:20:07 +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 wA1JK7cu040157; Thu, 1 Nov 2018 19:20:07 GMT (envelope-from sunpoet@FreeBSD.org) Received: (from sunpoet@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id wA1JK6Br040156; Thu, 1 Nov 2018 19:20:06 GMT (envelope-from sunpoet@FreeBSD.org) Message-Id: <201811011920.wA1JK6Br040156@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: sunpoet set sender to sunpoet@FreeBSD.org using -f From: Sunpoet Po-Chuan Hsieh Date: Thu, 1 Nov 2018 19:20:06 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r483730 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: sunpoet X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 483730 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.29 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: Thu, 01 Nov 2018 19:20:08 -0000 Author: sunpoet Date: Thu Nov 1 19:20:06 2018 New Revision: 483730 URL: https://svnweb.freebsd.org/changeset/ports/483730 Log: Document curl vulnerability Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Thu Nov 1 19:17:56 2018 (r483729) +++ head/security/vuxml/vuln.xml Thu Nov 1 19:20:06 2018 (r483730) @@ -58,6 +58,76 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + curl -- multiple vulnerabilities + + + curl + 7.14.17.60.0 + + + + +

curl security problems:

+
CVE-2018-16839: SASL password overflow via integer overflow
+
libcurl contains a buffer overrun in the SASL authentication code.
+
The internal function Curl_auth_create_plain_message fails to + correctly verify that the passed in lengths for name and password + aren't too long, then calculates a buffer size to allocate.
+
On systems with a 32 bit size_t, the math to calculate the buffer size + triggers an integer overflow when the user name length exceeds 2GB + (2^31 bytes). This integer overflow usually causes a very small buffer + to actually get allocated instead of the intended very huge one, making + the use of that buffer end up in a heap buffer overflow.
+
This bug is very similar to CVE-2017-14618.
+
It affects curl 7.33.0 to 7.61.1.
+
CVE-2018-16840: use-after-free in handle close
+
libcurl contains a heap use-after-free flaw in code related to closing + an easy handle.
+
When closing and cleaning up an "easy" handle in the Curl_close() + function, the library code first frees a struct (without nulling the + pointer) and might then subsequently erroneously write to a struct + field within that already freed struct.
+
It affects curl 7.59.0 to 7.61.1.
+
CVE-2018-16842: warning message out-of-buffer read
+
curl contains a heap out of buffer read vulnerability.
+
The command line tool has a generic function for displaying warning + and informational messages to stderr for various situations. For + example if an unknown command line argument is used, or passed to it in + a "config" file.
+
This display function formats the output to wrap at 80 columns. The + wrap logic is however flawed, so if a single word in the message is + itself longer than 80 bytes the buffer arithmetic calculates the + remainder wrong and will end up reading behind the end of the buffer. + This could lead to information disclosure or crash.
+
This vulnerability could lead to a security issue if used in this or + similar situations:
+
1. a server somewhere uses the curl command line to run something
+
2. if it fails, it shows stderr to the user
+
3. the server takes user input for parts of its command line input
+
4. user provides something overly long that triggers this crash
+
5. the stderr output may now contain user memory contents that wasn't + meant to be available
+
It affects curl 7.14.1 to 7.61.1.
+

+ + + + https://curl.haxx.se/docs/security.html + https://curl.haxx.se/docs/CVE-2018-16839.html + https://curl.haxx.se/docs/CVE-2018-16840.html + https://curl.haxx.se/docs/CVE-2018-16842.html + CVE-2018-16839 + CVE-2018-16840 + CVE-2018-16842 + + + 2018-10-31 + 2018-11-01 + + + Gitlab -- SSRF in Kubernetes integration