This page was not yet optimized for use on mobile devices.
CVE-2022-46175
Data ?
Vulnerability ID | CVE-2022-46175 |
---|---|
Published on | 24.12.2022 04:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:json5:json5:0.0.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:0.0.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:0.1.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:0.2.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:0.3.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:0.4.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:0.5.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:0.5.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:1.0.0:-:*:*:*:node.js:*:*,
cpe:2.3:a:json5:json5:1.0.0:beta:*:*:*:node.js:*:*,
…
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.