- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202008-23
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: chrony: Symlink vulnerability
     Date: August 30, 2020
     Bugs: #738154
       ID: 202008-23

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
A vulnerability in chrony may allow a privileged attacker to cause data
loss via a symlink.

Background
=========
chrony is a versatile implementation of the Network Time Protocol
(NTP).

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  net-misc/chrony              < 3.5.1                    >= 3.5.1

Description
==========
It was found that chrony did not check whether its PID file was a
symlink.

Impact
=====
A local attacker could perform symlink attack(s) to overwrite arbitrary
files with root privileges.

Workaround
=========
There is no known workaround at this time.

Resolution
=========
All chrony users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-misc/chrony-3.5.1"

References
=========
[ 1 ] CVE-2020-14367
      https://nvd.nist.gov/vuln/detail/CVE-2020-14367
[ 2 ] chrony-3.5.1 release announcement
      https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-announce/2020/08/msg00000.html

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202008-23

Concerns?
========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
======
Copyright 2020 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-202008-23: chrony: Symlink vulnerability

A vulnerability in chrony may allow a privileged attacker to cause data loss via a symlink.

Summary

It was found that chrony did not check whether its PID file was a symlink.

Resolution

All chrony users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=net-misc/chrony-3.5.1"

References

[ 1 ] CVE-2020-14367 https://nvd.nist.gov/vuln/detail/CVE-2020-14367 [ 2 ] chrony-3.5.1 release announcement https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-announce/2020/08/msg00000.html

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202008-23

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: Normal
Title: chrony: Symlink vulnerability
Date: August 30, 2020
Bugs: #738154
ID: 202008-23

Synopsis

A vulnerability in chrony may allow a privileged attacker to cause data loss via a symlink.

Background

chrony is a versatile implementation of the Network Time Protocol (NTP).

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-misc/chrony < 3.5.1 >= 3.5.1

Impact

===== A local attacker could perform symlink attack(s) to overwrite arbitrary files with root privileges.

Workaround

There is no known workaround at this time.

Related News