An issue was discovered in tls_verify_crl in ProFTPD through 1.3.6b. Failure to check for the appropriate field of a CRL entry (checking twice for subject, rather than once for subject and once for issuer) prevents some valid CRLs from being taken into account, and can allow clients whose certificates have been revoked to proceed with a connection to the server.
The product does not validate, or incorrectly validates, a certificate.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Proftpd | Proftpd | * | 1.3.5 (including) |
| Proftpd | Proftpd | 1.3.6 (including) | 1.3.6 (including) |
| Proftpd | Proftpd | 1.3.6-alpha (including) | 1.3.6-alpha (including) |
| Proftpd | Proftpd | 1.3.6-beta (including) | 1.3.6-beta (including) |
| Proftpd-dfsg | Ubuntu | bionic | * |
| Proftpd-dfsg | Ubuntu | disco | * |
| Proftpd-dfsg | Ubuntu | eoan | * |
| Proftpd-dfsg | Ubuntu | groovy | * |
| Proftpd-dfsg | Ubuntu | hirsute | * |
| Proftpd-dfsg | Ubuntu | impish | * |
| Proftpd-dfsg | Ubuntu | kinetic | * |
| Proftpd-dfsg | Ubuntu | lunar | * |
| Proftpd-dfsg | Ubuntu | mantic | * |
| Proftpd-dfsg | Ubuntu | trusty | * |
| Proftpd-dfsg | Ubuntu | xenial | * |