This page was not yet optimized for use on mobile devices.
CVE-2020-28012
Data ?
Vulnerability ID | CVE-2020-28012 |
---|---|
Published on | 06.05.2021 13:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:exim:exim:4.00:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.01:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.02:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.03:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.04:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.05:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.10:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.11:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.12:*:*:*:*:*:*:*,
cpe:2.3:a:exim:exim:4.14:*:*:*:*:*:*:*,
…
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.