This page was not yet optimized for use on mobile devices.
CVE-2016-1567
Data ?
Vulnerability ID | CVE-2016-1567 |
---|---|
Published on | 26.01.2016 19:59 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:tuxfamily:chrony:1.0:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.1:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.18:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.19:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.19.99.1:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.19.99.2:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.19.99.3:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.20:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.21:*:*:*:*:*:*:*,
cpe:2.3:a:tuxfamily:chrony:1.21:pre1:*:*:*:*:*:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.