This page was not yet optimized for use on mobile devices.
CVE-2016-5032
Data ?
Vulnerability ID | CVE-2016-5032 |
---|---|
Published on | 17.02.2017 17:59 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:libdwarf_project:libdwarf:1999-12-14:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2000-06-12:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2000-07-25:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2001-05-23:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2001-06-07:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2001-08-29:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2002-04:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2002-10-23:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2002-11-22:*:*:*:*:*:*:*,
cpe:2.3:a:libdwarf_project:libdwarf:2003-04-06:*:*:*:*:*:*:*,
…
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.