Certificate verification bypass via flawed connection reuse
Published Aug 5, 2021 · Updated Jun 9, 2025
Improper certificate validation in curl 7.10.4 through 7.77.0 allows remote attackers to receive data over a wrongly reused TLS connection. Curl_ssl_config_matches omits the issuer certificate and compares certificate-path fields without case sensitivity, treating distinct SSL configurations as equal. Exploitation requires reusable transfers to the same destination with different issuer certificates or case-colliding paths, and the reported impact is limited to confidentiality.
Summary
What happened
Improper certificate validation in curl 7.10.4 through 7.77.0 allows remote attackers to receive data over a wrongly reused TLS connection. Curl_ssl_config_matches omits the issuer certificate and compares certificate-path fields without case sensitivity, treating distinct SSL configurations as equal. Exploitation requires reusable transfers to the same destination with different issuer certificates or case-colliding paths, and the reported impact is limited to confidentiality.
The record
- CVE
- CVE-2021-22924
- Published
- Aug 5, 2021
- Updated
- Jun 9, 2025
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-20, CWE-295, CWE-706
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 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=curl 7.10.4 to and include curl 7.77.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 report 1223565proof 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