This page was not yet optimized for use on mobile devices.
CVE-2017-2825
Data ?
Vulnerability ID | CVE-2017-2825 |
---|---|
Published on | 20.04.2018 21:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:zabbix:zabbix:2.4.0:-:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.0:rc2:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.0:rc3:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.1:-:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.1:rc1:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.1:rc2:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.2:-:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.2:rc1:*:*:*:*:*:*,
cpe:2.3:a:zabbix:zabbix:2.4.3:-:*:*:*:*:*:*,
…
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.