CVE-2019-19270
published 2019-11-26CVE-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…
PriorityP336high7.5CVSS 3.1
AVNACLPRNUINSUCNIHAN
EPSS
1.01%
59.3th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | proftpd-dfsg | < proftpd-dfsg 1.3.6b-2 (bookworm) | proftpd-dfsg 1.3.6b-2 (bookworm) |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| proftpd | proftpd | <= 1.3.5 | — |
| proftpd | proftpd | — | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
osv7.5HIGH
vendor_debian7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2019-19270: proftpd-dfsg - An issue was discovered in tls_verify_crl in ProFTPD through 1.3.6b. Failure to ...
vendor_debian·2019·CVSS 7.5
CVE-2019-19270 [HIGH] CVE-2019-19270: proftpd-dfsg - An issue was discovered in tls_verify_crl in ProFTPD through 1.3.6b. Failure to ...
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.
Scope: local
bookworm: resolved (fixed in 1.3.6b-2)
bullseye: resolved (fixed in 1.3.6b-2)
forky: resolved (fixed in 1.3.6b-2)
sid: resolved (fixed in 1.3.6b-2)
trixie: resolved (fixed in 1.3.6b-2)
GHSA
GHSA-5pjj-3qp3-rjg3: An issue was discovered in tls_verify_crl in ProFTPD through 1
ghsa_unreviewed·2022-05-24
CVE-2019-19270 [MEDIUM] GHSA-5pjj-3qp3-rjg3: An issue was discovered in tls_verify_crl in ProFTPD through 1
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.
OSV
CVE-2019-19270: An issue was discovered in tls_verify_crl in ProFTPD through 1
osv·2019-11-26·CVSS 7.5
CVE-2019-19270 [HIGH] CVE-2019-19270: An issue was discovered in tls_verify_crl in ProFTPD through 1
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account [epel-all]
bugzilla·2019-11-29·CVSS 7.5
CVE-2019-19270 [HIGH] CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account [epel-all]
CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg c
Bugzilla
CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account [fedora-all]
bugzilla·2019-11-29·CVSS 7.5
CVE-2019-19270 [HIGH] CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account [fedora-all]
CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedp
Bugzilla
CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account
bugzilla·2019-11-29·CVSS 7.5
CVE-2019-19270 [HIGH] CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account
CVE-2019-19270 proftpd: failure to check for the appropriate field of a CRL entry prevents some valid CRLs from being taken into account
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.
Reference:
https://github.com/proftpd/proftpd/issues/859
Discussion:
Created proftpd tracking bugs for this issue:
Affects: epel-all [bug 1778261]
Affects: fedora-all [bug 1778260]
---
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a packa
http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00009.htmlhttps://github.com/proftpd/proftpd/issues/859https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OGBBCPLJSDPFG5EI5P5G7P4KEX7YSD5G/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QR65XUHPCRU3NXTSFVF2J4GWRIHC7AHW/http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00009.htmlhttps://github.com/proftpd/proftpd/issues/859https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OGBBCPLJSDPFG5EI5P5G7P4KEX7YSD5G/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QR65XUHPCRU3NXTSFVF2J4GWRIHC7AHW/
2019-11-26
Published