CVE-2020-14367

chrony: Insecure writing to PID file

Published Aug 24, 2020 CVSS 3.1 · 6.0 Medium EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2020-6508 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.
Ubuntu USN Ubuntu USN USN-4475-1 Chrony vulnerability
History
Type Values Removed Values Added
Metrics epss

{'score': 0.0033}

epss

{'score': 0.00284}

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Aug 4, 2024, 12:46 PM
Reserved
Jun 17, 2020, 12:00 AM
Status
Modified
Published
Aug 24, 2020, 3:15 PM
Modified
Jun 17, 2026, 2:54 AM
Severity
Moderate
Public date
Aug 19, 2020, 5:10 PM