This page was not yet optimized for use on mobile devices.
CVE-2010-4221
Data ?
Vulnerability ID | CVE-2010-4221 |
---|---|
Published on | 09.11.2010 21:00 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:proftpd:proftpd:1.3.2:*:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:a:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:b:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:c:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:d:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:e:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:rc1:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:rc2:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:rc3:*:*:*:*:*:*, cpe:2.3:a:proftpd:proftpd:1.3.2:rc4:*:*:*:*:*:*
-
…
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.