This page was not yet optimized for use on mobile devices.
CVE-2023-51713
Data ?
Vulnerability ID | CVE-2023-51713 |
---|---|
Published on | 22.12.2023 03:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:proftpd:proftpd:1.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.0:pre10:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.0:pre9:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.0:rc2:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.0:rc3:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.1:*:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.2:*:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.2:rc1:*:*:*:*:*:*,
cpe:2.3:a:proftpd:proftpd:1.2.2: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.