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

Configuration 1 (hide)

cpe:2.3:a:tuxfamily:chrony:*:*:*:*:*:*:*:*

Configuration 2 (hide)

cpe:2.3:o:fedoraproject:fedora:32:*:*:*:*:*:*:*

Configuration 3 (hide)

OR cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
cpe:2.3:o:canonical:ubuntu_linux:20.04:*:*:*:lts:*:*:*

History

No history.

Information

Published : 2020-08-24 15:15

Updated : 2023-11-07 03:17


NVD link : CVE-2020-14367

Mitre link : CVE-2020-14367

CVE.ORG link : CVE-2020-14367


JSON object : View

Products Affected

canonical

  • ubuntu_linux

fedoraproject

  • fedora

tuxfamily

  • chrony
CWE
CWE-59

Improper Link Resolution Before File Access ('Link Following')