This page was not yet optimized for use on mobile devices.
CVE-2022-0570
Data
| Vulnerability ID | CVE-2022-0570 |
|---|---|
| Published on | 14.02.2022 12:15 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:mruby:mruby:-:*:*:*:*:*:*:*,
cpe:2.3:a:mruby:mruby:-:*:*:*:*:ruby:*:*,
cpe:2.3:a:mruby:mruby:1.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:mruby:mruby:1.0.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:mruby:mruby:1.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:mruby:mruby:1.1.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:mruby:mruby:1.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:mruby:mruby:1.2.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:mruby:mruby:1.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:mruby:mruby:1.3.0:*:*:*:*:ruby:*:*,
…
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.