This page was not yet optimized for use on mobile devices.
CVE-2020-8172
Data ?
Vulnerability ID | CVE-2020-8172 |
---|---|
Published on | 08.06.2020 14:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:nodejs:node.js:12.0.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:12.0.0:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:12.1.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:12.1.0:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:12.2.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:12.2.0:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:12.3.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:12.3.0:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:12.3.1:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:12.3.1:*:*:*:lts:*:*:*,
…
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.