Effect: Cookie attribute injection via domain, path, and name fields in @effect/platform makeCookie()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in @effect/platform 0.97.1 and effect 4.0.0-beta.103.
Effect is a TypeScript framework that consists of several packages that work together to help build TypeScript applications. From @effect/platform 0.1.0 until 0.97.1 and effect 4.0.0-beta.0 until 4.0.0-beta.103, the name, domain, and path fields passed to makeCookie() allow semicolon delimiters that serializeCookie() writes verbatim into Set-Cookie headers. A caller that supplies attacker-controlled values can append cookie attributes, including a broader Domain or, when the caller has not set those options itself, SameSite=None or Max-Age. Encoded cookie values and CR or LF characters remain unaffected. This can widen a cookie's scope or add otherwise-unset cookie attributes. This issue is fixed in @effect/platform 0.97.1 and effect 4.0.0-beta.103.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| @effect | >=0.1.0 <0.97.1 | ||
| Effect-TS | >=4.0.0-beta.0 <4.0.0-beta.103 | ||
| npm: @effect/platform | >=0.1.0 <0.97.1 | 0.97.1 | |
| npm: effect | >=4.0.0-beta.0 <4.0.0-beta.103 | 4.0.0-beta.103 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in effect (npm), strongest first
Embed
A live severity badge for an advisory, README or ticket