CVE-2020-14367
Last modified
CVE-2020-14367 is a medium-severity vulnerability rated 6/10 on the CVSS scale. 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. EPSS estimates a 0.48% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Tuxfamily | Chrony | < 3.5.1 |
| Fedoraproject | Fedora | 32 |
| Canonical | Ubuntu Linux | 18.04 |
| Canonical | Ubuntu Linux | 20.04 |
References
- https://bugzilla.redhat.com/show_bug.cgi?id=1870298Issue Tracking, Patch, Vendor Advisory
- https://security.gentoo.org/glsa/202008-23Third Party Advisory
- https://usn.ubuntu.com/4475-1/Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1870298Issue Tracking, Patch, Vendor Advisory
- https://security.gentoo.org/glsa/202008-23Third Party Advisory
- https://usn.ubuntu.com/4475-1/Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-14367?
How severe is CVE-2020-14367?
How do I fix CVE-2020-14367?
Are you affected by CVE-2020-14367?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
