EulerOS 2.0 SP8 : chrony (EulerOS-SA-2020-2509)

According to the version of the chrony package installed, the EulerOS installation on the remote host is affected by the following vulnerability : - 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...

NewStart CGSL CORE 5.05 / MAIN 5.05 : chrony Multiple Vulnerabilities (NS-SA-2020-0112)

The remote NewStart CGSL host, running version CORE 5.05 / MAIN 5.05, has chrony packages installed that are affected by multiple vulnerabilities: - Multiple integer overflows in pktlength.c in Chrony before 1.29 allow remote attackers to cause a denial of service crash via a crafted 1...

EulerOS 2.0 SP9 : chrony (EulerOS-SA-2020-2495)

According to the version of the chrony package installed, the EulerOS installation on the remote host is affected by the following vulnerability : - 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...

EulerOS 2.0 SP9 : chrony (EulerOS-SA-2020-2482)

According to the version of the chrony package installed, the EulerOS installation on the remote host is affected by the following vulnerability : - 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...

Huawei EulerOS: Security Advisory for chrony (EulerOS-SA-2020-2482)

The remote host is missing an update for the Huawei EulerOS SPDX-FileCopyrightText: 2020 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only ifdescription...

Huawei EulerOS: Security Advisory for chrony (EulerOS-SA-2020-2495)

The remote host is missing an update for the Huawei EulerOS SPDX-FileCopyrightText: 2020 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only ifdescription...

Medium: chrony

Issue Overview: A flaw was found in chrony 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...

Security fix for the ALT Linux 8 package chrony version 3.5.1-alt1

3.5.1-alt1 built Sept. 4, 2020 Anton Farygin in task 256941 Aug. 26, 2020 Anton Farygin - 3.5.1 fixes: CVE-2020-14367...

Amazon Linux AMI : chrony (ALAS-2020-1431)

The version of chrony installed on the remote host is prior to 3.2-1.27. It is, therefore, affected by a vulnerability as referenced in the ALAS-2020-1431 advisory. A flaw was found in chrony when creating the PID file under the /var/run/chrony folder. The file is created during chronyd startup...

Ubuntu: Security Advisory (USN-4475-1)

The remote host is missing an update for the SPDX-FileCopyrightText: 2020 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only ifdescription...

GLSA-202008-23 : chrony: Symlink vulnerability

The remote host is affected by the vulnerability described in GLSA-202008-23 chrony: Symlink vulnerability It was found that chrony did not check whether its PID file was a symlink. Impact : A local attacker could perform symlink attacks to overwrite arbitrary files with root privileges. Workarou...

Chrony Denial of Service Vulnerability (CNVD-2020-50554)

Chrony is a general-purpose implementation of the Network Time Protocol NTP that synchronizes the system clock with an NTP server. A denial of service exists in the Chrony product. The vulnerability stems from a network system or product that does not properly validate incoming data, and could be...

chrony: Symlink vulnerability

Background chrony is a versatile implementation of the Network Time Protocol NTP. Description It was found that chrony did not check whether its PID file was a symlink. Impact A local attacker could perform symlink attacks to overwrite arbitrary files with root privileges. Workaround There is no...

Ubuntu 18.04 LTS / 20.04 LTS : Chrony vulnerability (USN-4475-1)

The remote Ubuntu 18.04 LTS / 20.04 LTS host has a package installed that is affected by a vulnerability as referenced in the USN-4475-1 advisory. It was discovered that Chrony incorrectly handled certain symbolic links. An attacker could possibly use this issue to cause a denial of service or...

USN-4475-1: Chrony vulnerability

It was discovered that Chrony incorrectly handled certain symbolic links. An attacker could possibly use this issue to cause a denial of service or expose sensitive information...

USN-4475-1 chrony vulnerability

It was discovered that Chrony incorrectly handled certain symbolic links. An attacker could possibly use this issue to cause a denial of service or expose sensitive information...

Denial Of Service (DoS)

chrony is vulnerable to denial of service DoS. The vulnerability exists as 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 writin...

Fedora: Security Advisory for chrony (FEDORA-2020-7aa962c55e)

The remote host is missing an update for the Copyright C 2020 Greenbone Networks GmbH Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-or-later This program is free software; you can...

ALPINE-CVE-2020-14367

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...

CVE-2020-14367

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...