Vulnerabilities · 2016 · Tuxfamily
CVE-2016-1567
Tuxfamily Chrony vulnerability
chrony before 1.31.2 and 2.x before 2.2.1 do not verify peer associations of symmetric keys when authenticating packets, which might allow remote attackers to conduct impersonation attacks via an arbitrary trusted key, aka a "skeleton key."
Affected products
Chrony. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Tuxfamily Chrony runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- chrony.tuxfamily.org/news.html#_20_jan_2016_chrony_2_2_1_and_chrony_1_31_2_released · Vendor Advisory
- lists.fedoraproject.org/pipermail/package-announce/2016-January/175969.html · Patch
- www.talosintel.com/reports/TALOS-2016-0071/ · Exploit
- lists.fedoraproject.org/pipermail/package-announce/2016-February/176559.html
- nvd.nist.gov/vuln/detail/CVE-2016-1567
- cve.org/CVERecord?id=CVE-2016-1567
More vulnerabilities in Tuxfamily products
CVE-2020-14367CVE-2015-1853CVE-2015-1822CVE-2015-1821CVE-2012-4503CVE-2012-4502CVE-2010-0294CVE-2010-0293All 10
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.