CVE-2024-47764

Description

### 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

How to fix CVE-2024-47764

To remediate CVE-2024-47764, upgrade the affected package to a fixed version below.

• —no fix listed
• —upgrade to 0.7.0 or later

Is CVE-2024-47764 being exploited?

Low — EPSS is 0.2%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0
• from 0, < 0.7.0

CVSS scores

References (5)

• ADVISORYsecurity-tracker.debian.org/tracker/CVE-2024-47764
• PATCHgithub.com/jshttp/cookie
• WEBgithub.com/jshttp/cookie/commit/e10042845354fea83bd8f34af72475eed1dadf5c
• WEBgithub.com/jshttp/cookie/pull/167
• WEB