This page was not yet optimized for use on mobile devices.
CVE-2022-32096
Data ?
Vulnerability ID | CVE-2022-32096 |
---|---|
Published on | 13.07.2022 16:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.2:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.3:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.4:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.5:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.6:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.7:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.8:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.9:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.10:*:*:*:*:*:*:*,
cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.11:*:*:*:*:*:*:*,
…
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.