This page was not yet optimized for use on mobile devices.
CVE-2016-9829
Data ?
| Vulnerability ID | CVE-2016-9829 |
|---|---|
| Published on | 17.02.2017 02:59 |
| Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:libming:libming:0.3.0:-:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.3.0:beta2:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.4.0:beta3:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.4.0:beta4:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.4.0:beta5:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.4.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.4.0:rc2:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.4.3:*:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.4.4:*:*:*:*:*:*:*,
cpe:2.3:a:libming:libming:0.4.5:*:*:*:*:*:*:*,
…
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.