Skip to content
Fencer Vulns
high 7.5

CVE-2019-19270 json

An issue was discovered in tls_verify_crl in ProFTPD through 1.3.6b.

published 2019-11-26 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-8896

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

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.

Patch / fix

  • proftpd-dfsg Debian 14, Debian 13, Debian 12 1.3.6b-2

debian advisories DEBIAN-CVE-2019-19270

  • proftpd Package Hub 15 SP1, Package Hub 15, openSUSE Leap 15.1 1.3.6b-bp151.4.6.2

opensuse advisories openSUSE-SU-2020:0031-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-19270 updated cvss 6.5

proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.