This page was not yet optimized for use on mobile devices.
CVE-2016-8863
Data ?
Vulnerability ID | CVE-2016-8863 |
---|---|
Published on | 07.03.2017 16:59 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:libupnp_project:libupnp:1.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.4.2:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.4.3:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.4.4:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.4.5:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.4.6:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.4.7:*:*:*:*:*:*:*,
cpe:2.3:a:libupnp_project:libupnp:1.6.0:*:*:*:*:*:*:*,
…
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.