This page was not yet optimized for use on mobile devices.
CVE-2017-16611
Data ?
Vulnerability ID | CVE-2017-16611 |
---|---|
Published on | 01.12.2017 17:29 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:x:libxfont:1.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.2.1:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.2.2:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.2.3:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.2.4:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.2.5:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.2.6:*:*:*:*:*:*:*,
cpe:2.3:a:x:libxfont:1.2.7:*:*:*:*:*:*:*,
…
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.