This page was not yet optimized for use on mobile devices.
CVE-2022-1650
Data ?
Vulnerability ID | CVE-2022-1650 |
---|---|
Published on | 12.05.2022 11:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:eventsource:eventsource:0.0.1:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.2:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.3:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.4:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.5:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.6:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.7:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.8:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.9:*:*:*:node.js:*:*:*,
cpe:2.3:a:eventsource:eventsource:0.0.10:*:*:*: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.