CVE-2020-14367

Description

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.

Category

6.0
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.33%
Vendor Advisory fedoraproject.org Vendor Advisory gentoo.org Vendor Advisory ubuntu.com Vendor Advisory redhat.com
Affected: n/a Chrony
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2020-14367?
CVE-2020-14367 has been scored as a medium severity vulnerability.
How to fix CVE-2020-14367?
To fix CVE-2020-14367, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-14367 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-14367 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-14367?
CVE-2020-14367 affects n/a Chrony.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.