[17] cookie accepts cookie name, path, and domain with out of bounds characters #396

New issue

Open

opened 2024-10-15 19:01:40 +01:00 by Helpdesk · 0 comments

Helpdesk commented

2024-10-15 19:01:40 +01:00

Member

Package: cookie (npm)
Affected versions: < 0.7.0
Patched version: 0.7.0

Impact
The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, serialize("userName=; Max-Age=2592000; a", value) would result in "userName=; Max-Age=2592000; a=test", setting userName cookie to

Package: `cookie` (npm) Affected versions: `< 0.7.0` Patched version: `0.7.0` --- Impact The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, serialize("userName=<script>alert('XSS3')</script>; Max-Age=2592000; a", value) would result in "userName=<script>alert('XSS3')</script>; Max-Age=2592000; a=test", setting userName cookie to <script> and ignoring value. A similar escape can be used for path and domain, which could be abused to alter other fields of the cookie. Patches Upgrade to 0.7.0, which updates the validation for name, path, and domain. Workarounds Avoid passing untrusted or arbitrary values for these fields, ensure they are set by the application instead of user input. References jshttp/cookie#167