Security Advisory

CVE-2020-14367: chrony Pidfile Symlink Flaw

Last updated:
  • CVE-2020-14367

CVE-2020-14367 is a symlink flaw in chrony before 3.5.1: chronyd writes its pidfile while still running as root and follows a link planted in its run directory, so an attacker who already controls the chrony account can overwrite any file. NVD scores it 6.0. Buildroot, OpenWrt and Yocto shipped fixes or backports in 2020.

Vulnerability summary

CVSS base score

6

Medium severity

EPSS score (FIRST)

0.5%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2020-14367 · Source: NVD

Affected components

ComponentCPEVersion range
chrony (chronyd pidfile creation)cpe:2.3:a:tuxfamily:chrony:*:*:*:*:*:*:*:*before 3.5.1; fixed in 3.5.1 (2020-08-20) and 4.0 (NVD, chrony news)
Buildroot package chrony—3.4 from 2018-09-23 and 3.5 from 2019-09-15; security bump to 3.5.1 committed 2020-08-23 (Buildroot commit 15484553)
OpenWrt packages feed chrony (openwrt-19.07 branch)—3.5, built with --chronyrundir=/var/run/chrony and --with-user=chrony; updated to 3.5.1 on 2020-10-10 (OpenWrt packages commit b48575ef)
Yocto Project meta-networking chrony (dunfell branch)—recipe stays at 3.5 with CVE-2020-14367.patch backported (meta-openembedded commit 24830d14)

What does this mean for affected devices?

NVD describes CVE-2020-14367 as a flaw "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 chronyd "does not check for an existing symbolic link with the same file name." NVD records CWE-59 and scores it 6.0 (medium), vector CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H, for chrony before 3.5.1 (NVD). The high privileges in the vector are the chrony account itself: this is a step from that account to root, not a remote attack.

Matthias Gerstner of SUSE, who found it, explains the mechanism in his oss-security post of 2020-08-21. In chronyd's main(), write_pidfile() runs "with full root privileges, while the privilege drop logic is only performed later", and the file is opened with fopen(). The run directory is owned by the chrony user, and since chrony 3.4 the default pidfile sits inside it, so that account can replace chronyd.pid with a link to /etc/fstab or any other file. chrony's news page lists the fix in chrony 3.5.1, released 20 August 2020, as "Create new file when writing pidfile".

No CISA ICS advisory in CISA's CSAF repository names this CVE (searched 2026-11-17), so the device exposure comes through embedded Linux build systems that package chrony:

  • Buildroot carried chrony 3.4 from 2018-09-23 and 3.5 from 2019-09-15. Its security bump to 3.5.1 was committed on 2020-08-23 and quotes the upstream advisory text.
  • OpenWrt builds chrony with --chronyrundir=/var/run/chrony and --with-user=chrony, the exact layout the advisory describes. The openwrt-19.07 branch shipped 3.5 until the update to 3.5.1 of 2020-10-10, "Fixes CVE-2020-14367". The master branch moved from 3.5 to 4.0 one day earlier.
  • Yocto Project meta-networking kept the dunfell recipe at chrony 3.5 and added CVE-2020-14367.patch. A dunfell image therefore reports chrony 3.5 but is fixed.

That last case is the trap for SBOM-based matching: a plain version check flags a patched 3.5 build. The Debian Security Tracker shows the same pattern, with buster fixed in 3.4-4+deb10u1, and names the minimal backport commit used for 3.5.1. Debian rates the issue unimportant for its own package because its packaging moved chronyd.pid to /run from 3.1-3 onward.

Our NTP and chrony vulnerabilities in embedded firmware guide ranks this CVE below the remote NTP crashes: on a device with no interactive accounts it is a hardening finding. Our Yocto and Buildroot SBOM guide shows where a backported patch such as the dunfell one is recorded, and firmware diffing and patch analysis shows how to confirm it in the shipped binary. For other NTP daemon flaws, see CVE-2016-6301 in BusyBox ntpd and CVE-2013-5211 in ntp.org ntpd.

CVE-2020-14367 is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.00489, the 43rd percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).

To fix it, upgrade to chrony 3.5.1 or later, or apply the backport. Where neither is possible soon, set the pidfile directive to a path in a root-owned directory such as /run/chronyd.pid, which is what Debian's packaging does.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • Pidfile under /var/run/chrony created as root during startup; no check for an existing symbolic link; data loss and denial of service; CWE-59; CVSS 3.1 6.0 AV:L/AC:L/PR:H; chrony before 3.5.1; published 2020-08-24. — NVD
  • write_pidfile() is called with full root privileges before SYS_DropRoot(); fopen(); /run/chrony owned by chrony:chrony; default pidfile in /run/chrony since 3.4; symlink to /etc/fstab example; posted 2020-08-21 by Matthias Gerstner (SUSE). — oss-security
  • chrony-3.5.1 released 20 Aug 2020; security fix: Create new file when writing pidfile (CVE-2020-14367). — chrony news
  • package/chrony: security bump to version 3.5.1, authored 2020-08-21, committed 2020-08-23; earlier bumps to 3.4 (2018-09-23) and 3.5 (2019-09-15). — Buildroot
  • openwrt-19.07 chrony: update to 3.5.1, Fixes CVE-2020-14367, 2020-10-10; Makefile uses --chronyrundir=/var/run/chrony and --with-user=chrony; master updated 3.5 to 4.0 on 2020-10-09. — OpenWrt packages
  • meta-networking dunfell: chrony: Patch CVE-2020-14367; recipe chrony_3.5.bb lists CVE-2020-14367.patch (checked 2026-11-17). — meta-openembedded
  • Buster fixed in 3.4-4+deb10u1; unstable 3.5.1-1, unimportant; minimal backport f00fed20 for 3.5.1; Debian packaging relocates chronyd.pid to /run since 3.1-3. — Debian Security Tracker
  • Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.00489 (43rd percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. oss-security: chrony CVE-2020-14367, unsafe pidfile creation (Matthias Gerstner, SUSE)
  3. chrony news: chrony-3.5.1 released
  4. Buildroot commit: package/chrony security bump to version 3.5.1
  5. OpenWrt packages commit (openwrt-19.07): chrony update to 3.5.1
  6. meta-openembedded commit (dunfell): chrony patch CVE-2020-14367
  7. Debian Security Tracker
  8. CISA KEV
  9. FIRST EPSS

Frequently asked questions

Can CVE-2020-14367 be exploited over the network?

No. The attacker must already control the chrony user account to plant the symbolic link, and the attack runs when chronyd next starts as root. NVD's vector is local with high privileges (per NVD and the oss-security report).

Why does a scanner flag chrony 3.5 on a patched Yocto image?

The Yocto dunfell recipe keeps version 3.5 and applies CVE-2020-14367.patch, and Debian buster fixed it in 3.4-4+deb10u1. A plain version match against "before 3.5.1" reports both as affected, so check the patch list (per meta-openembedded and the Debian Security Tracker).

Which embedded build systems shipped a fix for CVE-2020-14367?

Buildroot bumped chrony to 3.5.1 on 2020-08-23, OpenWrt's 19.07 branch updated to 3.5.1 on 2020-10-10, and Yocto dunfell backported the patch onto 3.5 (per the Buildroot, OpenWrt packages and meta-openembedded commits).

Is CVE-2020-14367 in the CISA KEV catalog?

No, not as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.00489, the 43rd percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).