Cleartext data exposure via skipped TLS enforcement
Published Sep 29, 2021 · Updated Apr 16, 2026
TLS enforcement bypass in curl 7.20.0 through 7.78.0 allows remote attackers to expose cleartext data through crafted server replies. The FTP state machine accepts a 230 greeting as authenticated, while IMAP and POP3 capability-error paths begin authentication without enforcing the requested TLS upgrade. Exposure requires an IMAP, POP3, or FTP transfer configured with --ssl-reqd or the equivalent libcurl setting and lets the responding server or an on-path attacker read unencrypted credentials or content.
Summary
What happened
TLS enforcement bypass in curl 7.20.0 through 7.78.0 allows remote attackers to expose cleartext data through crafted server replies. The FTP state machine accepts a 230 greeting as authenticated, while IMAP and POP3 capability-error paths begin authentication without enforcing the requested TLS upgrade. Exposure requires an IMAP, POP3, or FTP transfer configured with --ssl-reqd or the equivalent libcurl setting and lets the responding server or an on-path attacker read unencrypted credentials or content.
The record
- CVE
- CVE-2021-22946
- Published
- Sep 29, 2021
- Updated
- Apr 16, 2026
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-325, CWE-319, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2021CVE publishedPublication date reported by the CVE source.
- Apr 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=curl 7.20.0 to and including 7.78.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Public HackerOne reproduction reportproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo