This page was not yet optimized for use on mobile devices.
CVE-2017-15132
Data ?
Vulnerability ID | CVE-2017-15132 |
---|---|
Published on | 25.01.2018 20:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:dovecot:dovecot:2.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0:-:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0:alpha2:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0:alpha3:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0:beta2:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0:beta3:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0:beta4:*:*:*:*:*:*,
cpe:2.3:a:dovecot:dovecot:2.0.0: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.