This page was not yet optimized for use on mobile devices.
CVE-2016-6304
Data ?
Vulnerability ID | CVE-2016-6304 |
---|---|
Published on | 26.09.2016 19:59 |
Severity | HIGH |
Vulnerable configurations ?
-
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.2:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.3:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.4:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.5:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.6:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.7:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.8:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:0.10.9:*:*:*:-:*:*:*,
…
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.