Skip to content

Update "cookie" npm dependency from v0.6.0 to fix CVE-2024-47764 #13399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
leonklingele opened this issue Jan 31, 2025 · 2 comments
Closed

Update "cookie" npm dependency from v0.6.0 to fix CVE-2024-47764 #13399

leonklingele opened this issue Jan 31, 2025 · 2 comments

Comments

@leonklingele
Copy link

Describe the bug

Saw this come up in our osv-scanner CI job:

+-------------------------------------+------+-----------+---------+---------+-------------------+
| OSV URL                             | CVSS | ECOSYSTEM | PACKAGE | VERSION | SOURCE            |
+-------------------------------------+------+-----------+---------+---------+-------------------+
| https://osv.dev/GHSA-pxg6-pf52-xh8x |      | npm       | cookie  | 0.6.0   | package-lock.json |
+-------------------------------------+------+-----------+---------+---------+-------------------+

Probably caused by

kit/pnpm-lock.yaml

Lines 348 to 350 in 09296d0

cookie:
specifier: ^0.6.0
version: 0.6.0
but saw some other references to the cookie package.

Even if SvelteKit might be unaffected by the issue, it still seems worth to update the package.

Also see https://osv.dev/vulnerability/GHSA-pxg6-pf52-xh8x and jshttp/cookie#167

Reproduction

Run nix-shell --pure -p osv-scanner go --run 'osv-scanner --no-ignore .' in a SvelteKit project.

Logs

System Info

Irrelevant.

Severity

annoyance

Additional Information

No response

@stephenlrandall
Copy link
Contributor

#13386

The issue is that upgrading cookie comes with breaking changes. But you can separately fix a version of cookie in your package.json file: #13089 (comment)

@leonklingele
Copy link
Author

Thanks, that clears things up.

@Conduitry Conduitry marked this as a duplicate of #13432 Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants