This page was not yet optimized for use on mobile devices.
CVE-2017-7418
Data ?
Vulnerability ID | CVE-2017-7418 |
---|---|
Published on | 04.04.2017 17:59 |
Severity | MEDIUM |
Vulnerable configurations ?
- cpe:2.3:a:proftpd:proftpd:1.3.2:d:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.4:d:*:*:*:*:*:*
-
cpe:2.3:a:proftpd:proftpd:1.3.6:*:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.3.6:-:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.3.6:a:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.3.6:alpha:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.3.6:b:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.3.6:beta:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.3.6:rc1:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.3.6:rc2:*:*:*:*:*:*,
…
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.