This page was not yet optimized for use on mobile devices.
CVE-2016-5180
Data ?
Vulnerability ID | CVE-2016-5180 |
---|---|
Published on | 03.10.2016 15:59 |
Severity | CRITICAL |
Vulnerable configurations ?
- cpe:2.3:a:c-ares_project:c-ares:1.11.0:*:*:*:*:*:*:*
- cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
-
cpe:2.3:a:nodejs:node.js:0.10.0:*:*:*:*:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.1:*:*:*:*:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.1:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.2:*:*:*:*:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.2:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.3:*:*:*:*:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.3:*:*:*:-:*:*:*,
…
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.