This page was not yet optimized for use on mobile devices.
CVE-2022-23221
Data ?
Vulnerability ID | CVE-2022-23221 |
---|---|
Published on | 19.01.2022 17:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:h2database:h2:1.1.101:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.102:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.103:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.104:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.105:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.106:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.107:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.108:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.109:*:*:*:*:*:*:*,
cpe:2.3:a:h2database:h2:1.1.110:*:*:*:*:*:*:*,
…
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.