CVE-2019-19270 · cross-distro fix matrix

CVE-2019-19270: 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 certificat

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2019-19270 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

proftpd-dfsg→ fixed in1.3.6b-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y proftpd-dfsg
```

Debian bookworm

Source: Debian Security Tracker

proftpd-dfsg→ fixed in1.3.6b-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y proftpd-dfsg
```

Debian trixie

Source: Debian Security Tracker

proftpd-dfsg→ fixed in1.3.6b-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y proftpd-dfsg
```

Are YOU affected by CVE-2019-19270?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2019-19270dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)