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 certificates have been revoked to proceed with a connection to the server.

Published: 2019-11-25 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-19270 is rated Moderate Risk (51.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.01%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-19270

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.20% 1.01% +0.82%
2 2025-04-07 0.15% 0.20% +0.05%
3 2025-03-30 — 0.15% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-19270

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-19270

OS Trackers for CVE-2019-19270

vendor priority summary link
debian not yet assigned CVE-2019-19270 not yet assigned priority: Debian including 1 source packages (proftpd-dfsg), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-19270
ubuntu medium CVE-2019-19270 medium priority: Ubuntu including 1 source packages (proftpd-dfsg), 18 status rows across 18 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 10, needs-triage 7, DNE 1. https://ubuntu.com/security/CVE-2019-19270

Affected software / configurations for CVE-2019-19270

Vendor Product Version Raw CPE
proftpd proftpd <= 1.3.5 cpe:2.3:a:proftpd:proftpd:*:*:*:*:*:*:*:*
proftpd proftpd 1.3.6 cpe:2.3:a:proftpd:proftpd:1.3.6:-:*:*:*:*:*:*
proftpd proftpd 1.3.6 cpe:2.3:a:proftpd:proftpd:1.3.6:alpha:*:*:*:*:*:*
proftpd proftpd 1.3.6 cpe:2.3:a:proftpd:proftpd:1.3.6:beta:*:*:*:*:*:*
fedoraproject fedora 30 cpe:2.3:o:fedoraproject:fedora:30:*:*:*:*:*:*:*
fedoraproject fedora 31 cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:*

References for CVE-2019-19270

cvelogic Threat Intelligence