VDB

CVE-2020-14367

CVE-2020-14367 PUBLISHED

Reported by redhat · Published August 24, 2020

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chronyAlpine3.5.1-r0, 3.4-r2
chronytuxfamily3.5.1

Affected products

VendorProductVersions
n/aChronyAll chrony versions before 3.5.1
alpinechrony0, 0
n/aChrony3.5.1
amazon:2chrony0

Timeline

  • Aug 24, 2020 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Aug 4, 2024 CVE Updated
  • Mar 6, 2026 Distribution Patch
  • Mar 6, 2026 Security Advisory (4 in total, the first dated here)
  • Sep 5, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2020-14367
vulnetix vdb fixes CVE-2020-14367

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-14367/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›