Security-prefix spoofing via decoded cookie names
Published Jan 1, 2022 · Updated May 22, 2025
Cookie prefix spoofing in Ruby 2.6.8 and earlier and CGI gem 0.3.0 and earlier allows remote attackers to alter application trust decisions. CGI::Cookie.parse URL-decodes attacker-controlled cookie names, allowing encoded names to acquire the reserved __Host- or __Secure- security prefixes after parsing. Exploitation requires an application to parse a crafted Cookie header and treat one of those prefixes as proof of browser-enforced security constraints.
Summary
What happened
Cookie prefix spoofing in Ruby 2.6.8 and earlier and CGI gem 0.3.0 and earlier allows remote attackers to alter application trust decisions. CGI::Cookie.parse URL-decodes attacker-controlled cookie names, allowing encoded names to acquire the reserved __Host- or __Secure- security prefixes after parsing. Exploitation requires an application to parse a crafted Cookie header and treat one of those prefixes as proof of browser-enforced security constraints.
The record
- CVE
- CVE-2021-41819
- Published
- Jan 1, 2022
- Updated
- May 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-565, T1606.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 1, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 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