Attribute injection via permissive serialization validation
Published Oct 4, 2024 · Updated Oct 4, 2024
Cookie attribute injection in jshttp cookie before 0.7.0 allows remote attackers to alter serialized cookie fields via untrusted inputs. The serialize function applies broad HTTP field-content validation to cookie names, values, domains, and paths, admitting separators that change downstream Set-Cookie parsing. Exposure requires an application to pass attacker-controlled data into those fields; injected delimiters can override attributes or discard the intended value.
Summary
What happened
Cookie attribute injection in jshttp cookie before 0.7.0 allows remote attackers to alter serialized cookie fields via untrusted inputs. The serialize function applies broad HTTP field-content validation to cookie names, values, domains, and paths, admitting separators that change downstream Set-Cookie parsing. Exposure requires an application to pass attacker-controlled data into those fields; injected delimiters can override attributes or discard the intended value.
The record
- CVE
- CVE-2024-47764
- Published
- Oct 4, 2024
- Updated
- Oct 4, 2024
- Vendor
- jshttp
- Product
- cookie
- Classifications
- CWE-74, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 4, 2024CVE publishedPublication date reported by the CVE source.
- Oct 4, 2024Record 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=< 0.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream serialize delimiter demonstrationproof of concept · demonstrated
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