Vulnerabilities · 2020 · Tuxfamily
CVE-2020-14367
Tuxfamily Chrony vulnerability
A flaw was found in chrony versions before 3.5.1 when creating the PID file under the /var/run/chrony folder. The file is created during chronyd startup while still running as the root user, and when it's opened for writing, chronyd does not check for an existing symbolic link with the same file name. This flaw allows an attacker with privileged access to create a symlink with the default PID file name pointing to any destination file in the system, resulting in data loss and a denial of service due to the path traversal.
Affected products
Chrony, Fedora, Ubuntu Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Tuxfamily Chrony runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- bugzilla.redhat.com/show_bug.cgi?id=1870298 · Patch
- security.gentoo.org/glsa/202008-23 · Third Party Advisory
- usn.ubuntu.com/4475-1/ · Third Party Advisory
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6
- nvd.nist.gov/vuln/detail/CVE-2020-14367
- cve.org/CVERecord?id=CVE-2020-14367
More vulnerabilities in Tuxfamily products
CVE-2016-1567CVE-2015-1853CVE-2015-1822CVE-2015-1821CVE-2012-4503CVE-2012-4502CVE-2010-0294CVE-2010-0293All 10
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.