Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 Aug 2020 10:08:38 +0000 (UTC)
From:      Matthias Andree <mandree@FreeBSD.org>
To:        ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   svn commit: r545757 - head/security/vuxml
Message-ID:  <202008221008.07MA8cTv034503@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
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.)
 -->
 <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">;
+  <vuln vid="719f06af-e45e-11ea-95a1-c3b8167b8026">
+    <topic>chrony &lt;= 3.5.1 data corruption through symlink vulnerability writing the pidfile</topic>
+    <affects>
+      <package>
+	<name>chrony</name>
+	<range><lt>3.5.1</lt></range>
+      </package>
+    </affects>
+    <description>
+      <body xmlns="http://www.w3.org/1999/xhtml">;
+	<p>Miroslav Lichvar reports:</p>
+	<blockquote cite="https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-announce/2020/08/msg00000.html">;
+	  <p>chrony-3.5.1 [...] fixes a security issue in writing of the pidfile.</p>
+	  <p>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.</p>
+	  <p>This issue was reported by Matthias Gerstner of SUSE.</p>
+	</blockquote>
+      </body>
+    </description>
+    <references>
+      <url>https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-announce/2020/08/msg00000.html</url>;
+      <cvename>CVE-2020-14367</cvename>
+    </references>
+    <dates>
+      <discovery>2020-08-06</discovery>
+      <entry>2020-08-22</entry>
+    </dates>
+  </vuln>
+
   <vuln vid="2ed7e8db-e234-11ea-9392-002590bc43be">
     <topic>sysutils/openzfs-kmod -- critical permissions issues</topic>
     <affects>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202008221008.07MA8cTv034503>