This page was not yet optimized for use on mobile devices.
CVE-2016-10328
Data ?
Vulnerability ID | CVE-2016-10328 |
---|---|
Published on | 14.04.2017 04:59 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:freetype:freetype:-:*:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:1.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:2.0:*:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:2.0.0:-:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:2.0.0:beta2:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:2.0.0:beta3:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:2.0.0:beta4:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:2.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:2.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:freetype:freetype:2.0.3:*:*:*:*:*:*:*,
…
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.