MEDIUM · 6.0

CVE-2020-14367

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 ...

Vulnerability 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.

CVSS Score

6.0

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
HIGH

Affected Products

VendorProductVersions
TuxfamilyChrony< 3.5.1
FedoraprojectFedora32
CanonicalUbuntu Linux18.04

Related Weaknesses (CWE)

References

FAQ

What is CVE-2020-14367?

CVE-2020-14367 is a vulnerability with a CVSS score of 6.0 (MEDIUM). 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 ...

How severe is CVE-2020-14367?

CVE-2020-14367 has been rated MEDIUM with a CVSS base score of 6.0/10. Review the CVSS metrics above for detailed severity breakdown.

Is there a patch for CVE-2020-14367?

Check the references section above for vendor advisories and patch information. Affected products include: Tuxfamily Chrony, Fedoraproject Fedora, Canonical Ubuntu Linux.