This page was not yet optimized for use on mobile devices.
CVE-2022-32212
Data ?
Vulnerability ID | CVE-2022-32212 |
---|---|
Published on | 14.07.2022 15:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:nodejs:node.js:14.0.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.1.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.2.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.3.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.4.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.5.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.6.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.7.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.8.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:14.9.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.