Svelte 1.22.1 is a minor patch release following closely on the heels of Svelte 1.22.0. Both versions champion Svelte's core philosophy of being a "magical disappearing UI framework," which translates to writing less boilerplate and shipping smaller, faster web applications. Examining the devDependencies reveals a comprehensive suite of tools for development, testing, and building. Both versions rely on the same versions of tools like Rollup for bundling, Babel for transpilation, and ESLint for code linting, ensuring a modern and robust development workflow.
The key difference lies in the release date, with version 1.22.1 being released just hours after 1.22.0. This suggests that 1.22.1 likely addresses a specific bug or issue identified immediately after the 1.22.0 release. For developers, this signifies the Svelte team's commitment to rapid issue resolution and maintaining a stable development experience. If you're building with Svelte, opting for the latest patch version is generally recommended. Especially take this in count when introducing new features. Both versions leverage a powerful ecosystem of tools, ensuring compatibility and facilitating efficient development, testing, and deployment.
All the vulnerabilities related to the version 1.22.1 of the package
Svelte vulnerable to XSS when using objects during server-side rendering
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.
Svelte has a potential mXSS vulnerability due to improper HTML escaping
A potential XSS vulnerability exists in Svelte for versions prior to 4.2.19.
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.
A vulnerable page (+page.svelte):
<script>
import { page } from "$app/stores"
// user input
let href = $page.url.searchParams.get("href") ?? "https://example.com";
</script>
<noscript>
<a href={href}>test</a>
</noscript>
If a user accesses the following URL,
http://localhost:4173/?href=</noscript><script>alert(123)</script>
then, alert(123) will be executed.
XSS, when using an attribute within a noscript tag