This page was not yet optimized for use on mobile devices.
CVE-2016-6262
Data ?
Vulnerability ID | CVE-2016-6262 |
---|---|
Published on | 07.09.2016 20:59 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:gnu:libidn:0.3:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.3.2:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.3.3:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.3.4:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.3.5:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.3.6:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.3.7:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:libidn:0.4:*:*:*:*:*:*:*,
…
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.