Conversation
🦋 Changeset detectedLatest commit: 7fd5434 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
For additional context, there is a CVE-2024-47764 regarding To fix this, the cookie validation has been narrowed: It is considered a Hence the version bump from Question is, would we have to wait for SvelteKit v3 for People will be receiving GitHub security alert digest emails regarding this:
|
|
Hi @hyunbinseo we're aware of this and looking into it. It's quite likely users will need to upgrade cookie themselves in the meantime and we can only upgrade cookie in kit v3 |
|
@eltigerchino, how to update manually? I don't have any cookies with |
|
You can use the override feature of your package manager. https://docs.npmjs.com/cli/v10/configuring-npm/package-json#overrides |
Svelte kit reverted the upgrade in sveltejs/kit#12767
This seems to be official:
|
Update to cookie 0.7.0. Since we were not using cookies, the security risks should have been minimal. The upgrade is accomplished with a manual override in package.json, see sveltejs/kit#12767. Fixes: https://github.com/dmoerner/pytorrent/security/dependabot/1
On doit la forcer (override) car il est impossibilité pour SvelteKit de mettre à jour cookie avant la v3. La version 0.7.0 contient un breaking change mais qui ne nous concerne pas. Voir : sveltejs/kit#12767
- To resolve low severity vulnerability - See sveltejs/kit#12767
- To resolve low severity vulnerability (see sveltejs/kit#12767) - Bump package versions
- To resolve low severity vulnerability (see sveltejs/kit#12767) - Bump package versions
- To resolve low severity vulnerability (see sveltejs/kit#12767) - Bump package versions
- To resolve low severity vulnerability (see sveltejs/kit#12767) - Bump package versions
SvelteKit 2.49.2 has cookie 0.6.0 wich has a security issue. The cookie inside the SvelteKit will probably be updated with version 3, then this workaround is no longer needed. see: sveltejs/kit#12767
* feat: tooltip option 1 option using small icon to display tooltip text * fix: wrong line * chore(ci): update dev ci to new ci pipeline by using default arguments for push-to and target * refactor: tooltip text added longer tooltip text Co-authored-by: Tobias Kussel <TKussel@users.noreply.github.com> * fix: npm audit updated all high and medium severity vulnerabilities. (Svelte had to be updated which needed an aditional <tbody> in ResultTable, and some other things for lint to pass) * fix: fixes for vite * fix: use cookie ^1.1.1 for security issue SvelteKit 2.49.2 has cookie 0.6.0 wich has a security issue. The cookie inside the SvelteKit will probably be updated with version 3, then this workaround is no longer needed. see: sveltejs/kit#12767 * fix: remove unused css Co-authored-by: Tobias Kussel <TKussel@users.noreply.github.com> * chore: remove unused variables (#17) * chore: remove unused variables * fix: npm audit for lens verify new code * fix: reset changes to package-lock.json --------- Co-authored-by: Tobias Kussel <tobias.kussel@dkfz-heidelberg.de> * feat(backend): Make sites optional for spot backend (#12) * chore: update Svelte and related dependencies (#16) * chore: update Svelte and related dependencies Bump Svelte to version 5.46.4 and update @sveltejs/kit and devalue to their latest versions. * fix: for run npm ci * fix: add spot sites to env for dev environment (#20) * fix: use package-lock in dockerfile and copy node_modules (#21) --------- Co-authored-by: Klein <paola.klein@dkfz-heidelberg.de> Co-authored-by: paola klein <56866655+paolaklein@users.noreply.github.com>
reverts #12746 . The major contains a breaking change where
:characters are no longer allowed in cookie namesPlease don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm testand lint the project withpnpm lintandpnpm checkChangesets
pnpm changesetand following the prompts. Changesets that add features should beminorand those that fix bugs should bepatch. Please prefix changeset messages withfeat:,fix:, orchore:.Edits