HTTP request denial via unbounded cookie accumulation
Published Jul 7, 2022 · Updated May 5, 2025
Denial of service in curl 7.71.0 through 7.83.1 allows remote attackers to interrupt HTTP requests via excessive Set-Cookie headers. curl stores every received cookie without per-response, outbound-count, or Cookie-header-size limits, so matching cookies can push a later request above its 1,048,576-byte internal ceiling and trigger an error. The target must enable cookie handling and contact the malicious server; domain matching can also block requests to a sibling host until the stored cookies expire or are removed.
Summary
What happened
Denial of service in curl 7.71.0 through 7.83.1 allows remote attackers to interrupt HTTP requests via excessive Set-Cookie headers. curl stores every received cookie without per-response, outbound-count, or Cookie-header-size limits, so matching cookies can push a later request above its 1,048,576-byte internal ceiling and trigger an error. The target must enable cookie handling and contact the malicious server; domain matching can also block requests to a sibling host until the stored cookies expire or are removed.
The record
- CVE
- CVE-2022-32205
- Published
- Jul 7, 2022
- Updated
- May 5, 2025
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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=Fixed in 7.84.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
- Original vulnerability report and reproductionproof 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