Traffic modification via proxy-origin session ticket confusion
Published Apr 1, 2021 · Updated Jun 9, 2025
Authentication bypass in curl 7.63.0 through 7.75.0 allows remote attackers controlling an HTTPS proxy to skip origin certificate checks. libcurl's TLS session cache failed to distinguish proxy and origin sessions, so a post-handshake TLS 1.3 ticket could resume the origin connection without its certificate check. Exploitation requires an OpenSSL-based build, TLS 1.3 to an HTTPS proxy, and a certificate accepted for the origin unless verification is disabled, enabling unnoticed traffic modification.
Summary
What happened
Authentication bypass in curl 7.63.0 through 7.75.0 allows remote attackers controlling an HTTPS proxy to skip origin certificate checks. libcurl's TLS session cache failed to distinguish proxy and origin sessions, so a post-handshake TLS 1.3 ticket could resume the origin connection without its certificate check. Exploitation requires an OpenSSL-based build, TLS 1.3 to an HTTPS proxy, and a certificate accepted for the origin unless verification is disabled, enabling unnoticed traffic modification.
The record
- CVE
- CVE-2021-22890
- Published
- Apr 1, 2021
- Updated
- Jun 9, 2025
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-300, CWE-290, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2021CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record 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=7.63.0 to and including 7.75.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
- HackerOne proof-of-concept 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