This page was not yet optimized for use on mobile devices.
CVE-2022-43516
Data ?
Vulnerability ID | CVE-2022-43516 |
---|---|
Published on | 05.12.2022 20:15 |
Severity | CRITICAL |
Vulnerable configurations ?
- cpe:2.3:a:microsoft:windows_firewall:-:*:*:*:*:*:*:*
- cpe:2.3:a:zabbix:zabbix:6.0.10:-:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:6.0.10:rc1:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:6.0.10:rc2:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:6.0.11:-:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:6.0.11:rc1:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:6.0.11:rc2:*:*:*:*:*:*
-
cpe:2.3:a:zabbix:zabbix:6.2.0:-:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:6.2.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:6.2.0:alpha2:*:*:*:*:*:*,
…
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.