Vulnerability in Tuxfamily Chrony
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.0 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H.
EPSS exploit prediction
EPSS 0.005, 42.6th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Tuxfamily Chrony
- Canonical Ubuntu Linux — versions 18.04, 20.04
- Fedoraproject Fedora — versions 32
- Chrony — versions All chrony versions before 3.5.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (Live-Hack-CVE/CVE-2020-14367, uemitarslan/suma_scripts). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- FEDORA-2020-7aa962c55e (vendor-advisory)
- bugzilla.redhat.com/show_bug.cgi (Patch, Issue Tracking, Vendor Advisory)
- GLSA-202008-23 (vendor-advisory, Third Party Advisory)
- USN-4475-1 (vendor-advisory, Third Party Advisory)