Svelte 1.41.4 represents a minor version bump over its predecessor, 1.41.3, within the Svelte framework ecosystem. Both versions share the same core description as "The magical disappearing UI framework," highlighting Svelte's unique approach to building web applications by compiling components to highly efficient vanilla JavaScript at build time. This compilation process results in smaller bundle sizes and improved runtime performance compared to traditional virtual DOM frameworks.
Key differences between the two versions lie primarily in their dependencies. Version 1.41.3 lists tslib as a direct dependency, while 1.41.4 moves this dependency to the devDependencies. The significance of this change is that tslib contains helper functions required for TypeScript code to function correctly and moving it to devDependencies suggests a potential shift in how the Svelte compiler handles TypeScript. This could mean improvements in how Svelte processes TypeScript code, possibly streamlining the compilation process or reducing the end-user's dependency footprint if they aren't using TypeScript.
Both versions rely on a robust suite of development dependencies, encompassing tools for testing (mocha, jsdom, nyc, codecov), linting (eslint, eslint-plugin-html, eslint-plugin-import), bundling (rollup and associated plugins), and general utilities (acorn, chalk, css-tree, prettier, magic-string, etc.). The presence of these tools underscores Svelte's commitment to a well-rounded developer experience, providing ample support for building, testing, and maintaining Svelte applications, making it easier for developers to produce high quality code. This rich ecosystem ensures developers have the necessary resources at their disposal.
All the vulnerabilities related to the version 1.41.4 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