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