First published: Tue Nov 26 2019(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Proftpd Proftpd | <=1.3.5 | |
Proftpd Proftpd | =1.3.6 | |
Proftpd Proftpd | =1.3.6-alpha | |
Proftpd Proftpd | =1.3.6-beta | |
Fedoraproject Fedora | =30 | |
Fedoraproject Fedora | =31 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2019-19270 is high with a severity value of 7.5.
CVE-2019-19270 impacts ProFTPD versions 1.3.5 and 1.3.6, potentially allowing clients with invalid certificates to be accepted.
You can check if your ProFTPD version is affected by CVE-2019-19270 by verifying if it is either 1.3.5 or 1.3.6.
The Common Weakness Enumeration (CWE) ID for CVE-2019-19270 is CWE-295.
Yes, there are references available for CVE-2019-19270. You can find them at: [reference 1], [reference 2], [reference 3].