This page was not yet optimized for use on mobile devices.
CVE-2023-39332
Data ?
Vulnerability ID | CVE-2023-39332 |
---|---|
Published on | 18.10.2023 04:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:nodejs:node.js:20.0.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.1.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.2.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.3.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.3.1:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.4.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.5.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.5.1:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.6.0:*:*:*:-:*:*:*,
cpe:2.3:a:nodejs:node.js:20.6.1:*:*:*:-:*:*:*,
…
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.