CVE-2024-47764: cookie accepts cookie name, path, and domain with out of bounds characters
Impact The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, serialize("userName= alert('XSS3') ; Max-Age=2592000; a", value) would result in "userName= alert('XSS3') ; Max-Age=2592000; a=test", setting userName cookie to and ignoring value. A similar escape can be used for path and domain, which could be abused to alter other fields of the cookie.
Published Oct 4, 2024 · Updated Apr 15, 2025
Affected packages
cookie
- Ecosystem
- npm
- Affected
- < 0.7.0
- Fixed in
- 0.7.0
- Check
npm ls cookie
Advisory details
From the GitHub Advisory Database (CC BY 4.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
- https://github.com/jshttp/cookie/pull/167
Credited to bewinsnw.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
