From owner-svn-ports-all@freebsd.org Mon Feb 11 18:59:53 2019 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 EB1EF14E09F7; Mon, 11 Feb 2019 18:59:52 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7AFD884F5B; Mon, 11 Feb 2019 18:59:52 +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 C7EF84263; Mon, 11 Feb 2019 18:59:48 +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 x1BIxmIl048499; Mon, 11 Feb 2019 18:59:48 GMT (envelope-from sunpoet@FreeBSD.org) Received: (from sunpoet@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x1BIxmHj048498; Mon, 11 Feb 2019 18:59:48 GMT (envelope-from sunpoet@FreeBSD.org) Message-Id: <201902111859.x1BIxmHj048498@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: sunpoet set sender to sunpoet@FreeBSD.org using -f From: Sunpoet Po-Chuan Hsieh Date: Mon, 11 Feb 2019 18:59:48 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r492723 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: sunpoet X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 492723 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 7AFD884F5B X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.97 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; NEURAL_HAM_SHORT(-0.97)[-0.969,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Mon, 11 Feb 2019 18:59:53 -0000 Author: sunpoet Date: Mon Feb 11 18:59:48 2019 New Revision: 492723 URL: https://svnweb.freebsd.org/changeset/ports/492723 Log: Update openjpeg status There were 5 vulnerabilities in openjpeg and 4 of them are fixed. The current status is described in [1] as follows: - CVE-2017-17479 and CVE-2017-17480 were fixed in r477112. - CVE-2018-5785 was fixed in r480624. - CVE-2018-6616 was fixed in r489415. - CVE-2018-5727 is not fixed yet. Though I keep committing fixes and updating the status, it does not show in the "pkg audit" result. Users have to follow the link but apparently few people would do that. Therefore, I got mails asking if the CVEs are fixed, etc. I don't know if there's a better way to handle this condition (partly fixed over several months). Instead of removing fixed CVEs from vuln.xml, I decided to add a new entry (5efd7a93-2dfb-11e9-9549-e980e869c2e9) which is split from the old entry (11dc3890-0e64-11e8-99b0-d017c2987f9a). It should be clearer for users if they only read the "pkg audit" result. [1] https://www.vuxml.org/freebsd/11dc3890-0e64-11e8-99b0-d017c2987f9a.html Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Mon Feb 11 18:59:42 2019 (r492722) +++ head/security/vuxml/vuln.xml Mon Feb 11 18:59:48 2019 (r492723) @@ -58,6 +58,36 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + OpenJPEG -- integer overflow + + + openjpeg + 2.3.0_3 + + + + +

SO-AND-SO reports:

+
+

In OpenJPEG 2.3.0, there is an integer overflow vulnerability in the + opj_t1_encode_cblks function (openjp2/t1.c). Remote attackers could + leverage this vulnerability to cause a denial of service via a crafted + bmp file.

+
+ + + + https://nvd.nist.gov/vuln/detail/CVE-2018-5727 + https://github.com/uclouvain/openjpeg/issues/1053 + CVE-2018-5727 + + + 2017-12-08 + 2019-02-11 + + + FreeBSD -- File description reference count leak @@ -6429,39 +6459,36 @@ a PingInterval period.

openjpeg - 2.3.0_3 + 2.3.0_3

OpenJPEG reports:

-
+

Multiple vulnerabilities have been found in OpenJPEG, the opensource JPEG 2000 codec. Please consult the CVE list for further details.

CVE-2017-17479 and CVE-2017-17480 were fixed in r477112.

CVE-2018-5785 was fixed in r480624.

CVE-2018-6616 was fixed in r489415.

-

CVE-2018-5727 is not fixed yet.

https://nvd.nist.gov/vuln/detail/CVE-2017-17479 https://nvd.nist.gov/vuln/detail/CVE-2017-17480 - https://nvd.nist.gov/vuln/detail/CVE-2018-5727 https://nvd.nist.gov/vuln/detail/CVE-2018-5785 https://nvd.nist.gov/vuln/detail/CVE-2018-6616 CVE-2017-17479 CVE-2017-17480 - CVE-2018-5727 CVE-2018-5785 CVE-2018-6616 2017-12-08 2018-07-27 - 2019-01-05 + 2019-02-11