This page was not yet optimized for use on mobile devices.
CVE-2016-5767
Data ?
Vulnerability ID | CVE-2016-5767 |
---|---|
Published on | 07.08.2016 10:59 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:libgd:libgd:1.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.6.0:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.6.1:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.6.2:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.6.3:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.7.0:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.7.1:*:*:*:*:*:*:*,
cpe:2.3:a:libgd:libgd:1.7.2:*:*:*:*:*:*:*,
…
running on/with
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.