From owner-svn-ports-all@freebsd.org Sat Aug 22 10:08:39 2020 Return-Path: Delivered-To: svn-ports-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5D2B13B5704; Sat, 22 Aug 2020 10:08:39 +0000 (UTC) (envelope-from mandree@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4BYYxg1lfGz4QjN; Sat, 22 Aug 2020 10:08:39 +0000 (UTC) (envelope-from mandree@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 2067F14A36; Sat, 22 Aug 2020 10:08:39 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 07MA8d8X034505; Sat, 22 Aug 2020 10:08:39 GMT (envelope-from mandree@FreeBSD.org) Received: (from mandree@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 07MA8cTv034503; Sat, 22 Aug 2020 10:08:38 GMT (envelope-from mandree@FreeBSD.org) Message-Id: <202008221008.07MA8cTv034503@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: mandree set sender to mandree@FreeBSD.org using -f From: Matthias Andree Date: Sat, 22 Aug 2020 10:08:38 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r545757 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: mandree X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 545757 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.33 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: Sat, 22 Aug 2020 10:08:39 -0000 Author: mandree Date: Sat Aug 22 10:08:38 2020 New Revision: 545757 URL: https://svnweb.freebsd.org/changeset/ports/545757 Log: vuln.xml: add chrony < 3.5.1 pidfile symlink vulnerability Security: 719f06af-e45e-11ea-95a1-c3b8167b8026 Security: CVE-2020-14367 Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Sat Aug 22 09:53:14 2020 (r545756) +++ head/security/vuxml/vuln.xml Sat Aug 22 10:08:38 2020 (r545757) @@ -58,6 +58,40 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + chrony <= 3.5.1 data corruption through symlink vulnerability writing the pidfile + + + chrony + 3.5.1 + + + + +

Miroslav Lichvar reports:

+
chrony-3.5.1 [...] fixes a security issue in writing of the pidfile.
+
When chronyd is configured to save the pidfile in a directory where the + chrony user has write permissions (e.g. /var/run/chrony - the default + since chrony-3.4), an attacker that compromised the chrony user account + could create a symbolic link at the location of the pidfile to make + chronyd starting with root privileges follow the symlink and write its + process ID to a file for which the chrony user doesn't have write + permissions, causing a denial of service, or data loss.
+
This issue was reported by Matthias Gerstner of SUSE.
+

+ + + + https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-announce/2020/08/msg00000.html + CVE-2020-14367 + + + 2020-08-06 + 2020-08-22 + + + sysutils/openzfs-kmod -- critical permissions issues