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.6.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)

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3ada729

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[eltigerchino]

Note: the new version of the cookie parser adheres more strictly to the RFC which will prevent cookie names from containing : , etc. causing it to be a breaking change.

[derkbell]

Any ETA on this or can I help on getting this merged? I have a failing CI audit check because of the cookie vulnerability

[eltigerchino]

Any ETA on this or can I help on getting this merged? I have a failing CI audit check because of the cookie vulnerability

You'll need to use an override to install cookie 0.7.0 since we can't merge this without it being a breaking change. You'll have to wait until SvelteKit 3 or if we can find another workaround.

[derkbell]

Thanks for your swift reply, I didn't know about the overrides, learned something new today. This works for now.

[Rich-Harris]

preview: https://svelte-dev-git-preview-kit-12768-svelte.vercel.app/

this is an automated message

[elikoga]

They released cookie v1

Now is a good time to revive this and make the breaking change

cookie v1.0.2 loosened the restrictions.

https://github.com/jshttp/cookie/pull/210/files#diff-5634da488288c9045d2eb8425e64076d2c19211aefe3e531ca0087f3ab7794d0R38

updating to v1 is no longer breaking, only the version range 0.7.0-1.0.1 is bad

[eltigerchino]

duplicate of #13386

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^0.7.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.