This page was not yet optimized for use on mobile devices.
CVE-2016-1531
Data ?
Vulnerability ID | CVE-2016-1531 |
---|---|
Published on | 07.04.2016 23:59 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:exim:exim:-:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:2.10:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:2.11:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:2.12:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:3.00:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:3.01:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:3.02:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:3.03:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:3.10:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:3.11:*:*:*:*:*:*:*,
…
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.