This page was not yet optimized for use on mobile devices.
CVE-2016-4338
Data ?
Vulnerability ID | CVE-2016-4338 |
---|---|
Published on | 23.01.2017 21:59 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:zabbix:zabbix:2.0.0:*:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:2.0.0:-:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:2.0.0:rc1:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:2.0.0:rc2:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:2.0.0:rc3:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:2.0.0:rc4:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:2.0.0:rc5:*:*:*:*:*:*, cpe:2.3:a:zabbix:zabbix:2.0.0:rc6:*:*:*:*:*:*
-
cpe:2.3:a:zabbix:zabbix:2.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.0.1:-:*:*:*:*:*:*,
…
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.