This page was not yet optimized for use on mobile devices.
CVE-2023-32002
Data ?
Vulnerability ID | CVE-2023-32002 |
---|---|
Published on | 21.08.2023 17:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:nodejs:node.js:16.0.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:16.0.0:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:16.1.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:16.2.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:16.3.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:16.4.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:16.4.1:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:16.4.2:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:16.5.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:16.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.