@effect/platform cookie attribute injection in makeCookie()
Effect-TS effect · @effect platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @effect/platform npm |
|
|
| effect npm |
|
|
Effect-TS effect · @effect platform
| Product | Affected | Fixed in |
|---|---|---|
| @effect/platform npm |
|
|
| effect npm |
|
|
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.
From the CVE record · GitHub_M
The name, domain, and path fields passed to makeCookie() can contain semicolons that serializeCookie() writes verbatim into Set-Cookie headers. If a caller supplies attacker-controlled values, an attacker can widen a cookie’s domain or add otherwise-unset attributes such as SameSite=None or Max-Age. The input does not specify a network or local attack path, authentication requirement, or user interaction.
Check applications using npm @effect/platform versions >=0.1.0 <0.97.1 or effect versions >=4.0.0-beta.0 <4.0.0-beta.103.