This page was not yet optimized for use on mobile devices.
CVE-2022-29221
Data ?
Vulnerability ID | CVE-2022-29221 |
---|---|
Published on | 24.05.2022 15:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:smarty:smarty:1.0:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.0a:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.0b:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.2.1:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.2.2:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:smarty:smarty:1.3.2:*:*:*:*:*:*:*,
…
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.