chore(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.

[cloudflare-workers-and-pages]

Deploying authjs-nuxt with    Cloudflare Pages

Latest commit:	175acbe
Status:	🚫  Build failed.

View logs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 175acbe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR