Open renovate[bot] opened 2 years ago
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:
The artifact failure details are included below:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @sveltejs/kit@1.0.0-next.287
npm ERR! Found: svelte@4.2.19
npm ERR! node_modules/svelte
npm ERR! dev svelte@"4.2.19" from the root project
npm ERR! peer svelte@">=3.19.0" from svelte-hmr@0.14.9
npm ERR! node_modules/svelte-hmr
npm ERR! svelte-hmr@"^0.14.9" from @sveltejs/vite-plugin-svelte@1.0.0-next.38
npm ERR! node_modules/@sveltejs/vite-plugin-svelte
npm ERR! @sveltejs/vite-plugin-svelte@"^1.0.0-next.32" from @sveltejs/kit@1.0.0-next.287
npm ERR! node_modules/@sveltejs/kit
npm ERR! dev @sveltejs/kit@"1.0.0-next.287" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer svelte@"^3.44.0" from @sveltejs/kit@1.0.0-next.287
npm ERR! node_modules/@sveltejs/kit
npm ERR! dev @sveltejs/kit@"1.0.0-next.287" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: svelte@3.59.2
npm ERR! node_modules/svelte
npm ERR! peer svelte@"^3.44.0" from @sveltejs/kit@1.0.0-next.287
npm ERR! node_modules/@sveltejs/kit
npm ERR! dev @sveltejs/kit@"1.0.0-next.287" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-08-30T18_42_50_001Z-debug-0.log
This PR contains the following updates:
3.46.4
->4.2.19
GitHub Vulnerability Alerts
CVE-2022-25875
The package svelte before 3.49.0 is vulnerable to Cross-site Scripting (XSS) due to improper input sanitization and to improper escape of attributes when using objects during SSR (Server-Side Rendering). Exploiting this vulnerability is possible via objects with a custom toString() function.
CVE-2024-45047
Summary
A potential XSS vulnerability exists in Svelte for versions prior to 4.2.19.
Details
Svelte improperly escapes HTML on server-side rendering. It converts strings according to the following rules:
"
->"
&
->&
<
-><
&
->&
The assumption is that attributes will always stay as such, but in some situation the final DOM tree rendered on browsers is different from what Svelte expects on server-side rendering. This may be leveraged to perform XSS attacks. More specifically, this can occur when injecting malicious content into an attribute within a
<noscript>
tag.PoC
A vulnerable page (
+page.svelte
):If a user accesses the following URL,
then,
alert(123)
will be executed.Impact
XSS, when using an attribute within a noscript tag
Release Notes
sveltejs/svelte (svelte)
### [`v4.2.19`](https://redirect.github.com/sveltejs/svelte/releases/tag/svelte%404.2.19) [Compare Source](https://redirect.github.com/sveltejs/svelte/compare/svelte@4.2.18...svelte@4.2.19) ##### Patch Changes - fix: ensure typings for `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.
This PR was generated by Mend Renovate. View the repository job log.