UBUNTU-CVE-2020-14367 (CVE-2020-14367)
Vulnerability from osv_ubuntu – Published: 2020-08-24 15:15 – Updated: 2025-10-24 04:48 – Source websiteA 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.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "chrony",
"binary_version": "1.29-1ubuntu0.1+esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "chrony",
"purl": "pkg:deb/ubuntu/chrony@1.29-1ubuntu0.1+esm1?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.26-4",
"1.29-1",
"1.29-1ubuntu0.1",
"1.29-1ubuntu0.1+esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "chrony",
"binary_version": "2.1.1-1ubuntu0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "chrony",
"purl": "pkg:deb/ubuntu/chrony@2.1.1-1ubuntu0.1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.30-2",
"1.31.1-2",
"2.1.1-1",
"2.1.1-1ubuntu0.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "chrony",
"binary_version": "3.2-4ubuntu4.5"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "chrony",
"purl": "pkg:deb/ubuntu/chrony@3.2-4ubuntu4.5?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.2-4ubuntu4.5"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1-5",
"3.2-1build1",
"3.2-1ubuntu3",
"3.2-2",
"3.2-2ubuntu2",
"3.2-2ubuntu3",
"3.2-4ubuntu1",
"3.2-4ubuntu2",
"3.2-4ubuntu3",
"3.2-4ubuntu4",
"3.2-4ubuntu4.1",
"3.2-4ubuntu4.2",
"3.2-4ubuntu4.4"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "chrony",
"binary_version": "3.5-6ubuntu6.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "chrony",
"purl": "pkg:deb/ubuntu/chrony@3.5-6ubuntu6.2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.5-6ubuntu6.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.5-2ubuntu2",
"3.5-2ubuntu3",
"3.5-4ubuntu2",
"3.5-5ubuntu1",
"3.5-6ubuntu1",
"3.5-6ubuntu2",
"3.5-6ubuntu3",
"3.5-6ubuntu5",
"3.5-6ubuntu6",
"3.5-6ubuntu6.1"
]
}
],
"aliases": [],
"details": "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\u0027s 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.",
"id": "UBUNTU-CVE-2020-14367",
"modified": "2025-10-24T04:48:33Z",
"published": "2020-08-24T15:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-14367"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-4475-1"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-14367"
}
],
"related": [
"USN-4475-1"
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2020-14367"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.