This page was not yet optimized for use on mobile devices.
CVE-2022-22516
Data ?
Vulnerability ID | CVE-2022-22516 |
---|---|
Published on | 07.04.2022 19:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:codesys:control_rte_sl:3.0:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.8.60:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.9.40:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.9.50:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.9.60:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.9.70:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.10.0:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.10.10:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.10.20:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_rte_sl:3.5.10.40:*:*:*:*:*:*:*,
…
running on/with
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.