This page was not yet optimized for use on mobile devices.
CVE-2022-32471
Data ?
Vulnerability ID | CVE-2022-32471 |
---|---|
Published on | 15.02.2023 02:15 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:insyde:insydeh2o:5.0:*:*:*:*:*:*:*, cpe:2.3:a:insyde:insydeh2o:05.0a.11:*:*:*:*:*:*:*, cpe:2.3:a:insyde:insydeh2o:5.1:*:*:*:*:*:*:*, cpe:2.3:a:insyde:insydeh2o:5.2:*:*:*:*:*:*:*, cpe:2.3:a:insyde:insydeh2o:5.2.05.27.29:*:*:*:*:*:*:*
- cpe:2.3:a:insyde:insydeh2o:5.3:*:*:*:*:*:*:*, cpe:2.3:a:insyde:insydeh2o:5.3.05.36.29:*:*:*:*:*:*:*
- cpe:2.3:a:insyde:insydeh2o:5.4:*:*:*:*:*:*:*, cpe:2.3:a:insyde:insydeh2o:5.4.05.44.13:*:*:*:*:*:*:*
-
cpe:2.3:a:insyde:insydeh2o:5.5:*:*:*:*:*:*:*,
…
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.