This page was not yet optimized for use on mobile devices.
CVE-2022-38493
Data ?
| Vulnerability ID | CVE-2022-38493 |
|---|---|
| Published on | 20.08.2022 20:15 |
| Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.99:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.999:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:0.9.9999:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:1.0.0:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:1.1.0:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:1.1.1:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:1.1.2:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:1.1.3:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:1.1.4:*:*:*:*:*:*:*, cpe:2.3:a:rhonabwy_project:rhonabwy:1.1.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.