Sibling-site denial via control-byte cookies
Published Sep 23, 2022 · Updated May 5, 2025
Improper cookie validation in curl 4.9 through 7.84.0 allows remote attackers to block access to sibling HTTP(S) sites. Curl_cookie_add in lib/cookie.c stores cookie names and values containing control bytes instead of rejecting them. The attack requires the cookie engine to accept a crafted cookie from one site and later send it to a sibling whose server rejects the resulting request with HTTP 400.
Summary
What happened
Improper cookie validation in curl 4.9 through 7.84.0 allows remote attackers to block access to sibling HTTP(S) sites. Curl_cookie_add in lib/cookie.c stores cookie names and values containing control bytes instead of rejecting them. The attack requires the cookie engine to accept a crafted cookie from one site and later send it to a sibling whose server rejects the resulting request with HTTP 400.
The record
- CVE
- CVE-2022-35252
- Published
- Sep 23, 2022
- Updated
- May 5, 2025
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-1286, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 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 curl 7.85.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 1613943 proof of conceptproof 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