fix(deps): update dependency cookie to ^0.7.0 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cookie	^0.5.0 -> ^0.7.0

GitHub Vulnerability Alerts

CVE-2024-47764

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

---

Release Notes

jshttp/cookie (cookie)

v0.7.0: 0.7.0

Compare Source

• perf: parse cookies ~10% faster (#​144 by @​kurtextrem and #​170)
  • fix: narrow the validation of cookies to match RFC6265 (#​167 by @​bewinsnw)
  • fix: add main to package.json for rspack (#​166 by @​proudparrot2)

v0.6.0

Compare Source

==================

• Add partitioned option

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

➤ YN0000: ┌ Resolution step
➤ YN0002: │ @types/next@npm:9.0.0 doesn't provide react (p1468f), requested by next
➤ YN0002: │ @types/next@npm:9.0.0 doesn't provide react-dom (p25cb0), requested by next
➤ YN0002: │ next@npm:9.4.2 [62b05] doesn't provide typescript (p7c29c), requested by fork-ts-checker-webpack-plugin
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 2s 304ms
➤ YN0000: ┌ Fetch step
➤ YN0066: │ typescript@patch:typescript@npm%3A4.7.4#builtin<compat/typescript>::version=4.7.4&hash=cc6730: Cannot apply hunk #2 (set enableInlineHunks for details)
➤ YN0013: │ 6 packages were already cached, 987 had to be fetched
➤ YN0000: └ Completed in 1m 53s
➤ YN0000: Failed with errors in 1m 55s