Process memory corruption via proxy cleanup double free
Published Oct 29, 2022 · Updated May 7, 2025
Double free in curl and libcurl 7.77.0 through 7.85.0 allows attackers to corrupt process memory via a rejected HTTP proxy tunnel. Error cleanup in conn_shutdown frees the saved protocol structure while CONNECT cleanup still treats it as owned, causing the allocation to be released twice. Reachability requires an HTTP proxy to reject CONNECT for a dict, gopher, gophers, LDAP, LDAPS, RTMP, RTMPS, or Telnet transfer.
Summary
What happened
Double free in curl and libcurl 7.77.0 through 7.85.0 allows attackers to corrupt process memory via a rejected HTTP proxy tunnel. Error cleanup in conn_shutdown frees the saved protocol structure while CONNECT cleanup still treats it as owned, causing the allocation to be released twice. Reachability requires an HTTP proxy to reject CONNECT for a dict, gopher, gophers, LDAP, LDAPS, RTMP, RTMPS, or Telnet transfer.
The record
- CVE
- CVE-2022-42915
- Published
- Oct 29, 2022
- Updated
- May 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No public exploit references are available in this record.
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