This page was not yet optimized for use on mobile devices.
CVE-2016-10134
Data ?
Vulnerability ID | CVE-2016-10134 |
---|---|
Published on | 17.02.2017 02:59 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:zabbix:zabbix:1.0:*:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:*:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:-:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:beta10:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:beta11:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:beta12:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:beta2:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:beta3:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:beta4:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:1.1:beta5:*:*:*:*:*:*,
…
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.