First published: Wed Aug 19 2020(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/chrony | <3.5.1 | 3.5.1 |
ubuntu/chrony | <3.2-4ubuntu4.5 | 3.2-4ubuntu4.5 |
ubuntu/chrony | <3.5-6ubuntu6.2 | 3.5-6ubuntu6.2 |
ubuntu/chrony | <3.5.1-1ubuntu1 | 3.5.1-1ubuntu1 |
ubuntu/chrony | <3.5.1-1ubuntu1 | 3.5.1-1ubuntu1 |
ubuntu/chrony | <3.5.1-1ubuntu1 | 3.5.1-1ubuntu1 |
ubuntu/chrony | <3.5.1-1ubuntu1 | 3.5.1-1ubuntu1 |
ubuntu/chrony | <3.5.1-1ubuntu1 | 3.5.1-1ubuntu1 |
ubuntu/chrony | <3.5.1-1ubuntu1 | 3.5.1-1ubuntu1 |
ubuntu/chrony | <3.5.1-1ubuntu1 | 3.5.1-1ubuntu1 |
ubuntu/chrony | <3.5.1-1ubuntu1 | 3.5.1-1ubuntu1 |
ubuntu/chrony | <3.5.1-1 | 3.5.1-1 |
debian/chrony | 4.0-8+deb11u2 4.3-2+deb12u1 4.5-3 | |
Chrony | <3.5.1 | |
Fedora | =32 | |
Ubuntu Linux | =18.04 | |
Ubuntu Linux | =20.04 | |
Ubuntu | =18.04 | |
Ubuntu | =20.04 |
https://git.tuxfamily.org/chrony/chrony.git/patch/?id=f00fed20092b6a42283f29c6ee1f58244d74b545
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-14367 is considered a medium severity vulnerability due to the potential for privilege escalation.
To mitigate CVE-2020-14367, upgrade chrony to version 3.5.1 or later for affected systems.
Chrony versions prior to 3.5.1 are affected by CVE-2020-14367.
CVE-2020-14367 impacts chrony installations on several Linux distributions, including certain versions of Fedora and Ubuntu.
There is currently no evidence to suggest that CVE-2020-14367 is being actively exploited in the wild.