This page was not yet optimized for use on mobile devices.
CVE-2016-0028
Data ?
Vulnerability ID | CVE-2016-0028 |
---|---|
Published on | 16.06.2016 01:59 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:microsoft:exchange_server:2013:cumulative_update_11:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2013:cumulative_update_12:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2013:sp1:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2016:*:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2016:-:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2016:cumulative_update_1:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2016:cumulative_update_10:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2016:cumulative_update_11:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2016:cumulative_update_12:*:*:*:*:*:*,
cpe:2.3:a:microsoft:exchange_server:2016:cumulative_update_13:*:*:*:*:*:*,
…
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.