This page was not yet optimized for use on mobile devices.
CVE-2022-31179
Data ?
Vulnerability ID | CVE-2022-31179 |
---|---|
Published on | 01.08.2022 20:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:shescape_project:shescape:0.1.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:0.2.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:0.2.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:0.3.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:0.3.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:0.4.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:0.4.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:1.0.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:1.1.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:shescape_project:shescape:1.1.1:*:*:*:*:node.js:*:*,
…
running on/with
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.