Svelte version 2.15.2 is a minor patch release following 2.15.1 in the Svelte UI framework, known for its "disappearing" nature through compilation to highly efficient vanilla JavaScript. Both versions share the same core development dependencies, including tools like Rollup for bundling, TypeScript for type checking, and ESLint for code linting suggesting a stable and consistent development environment. Key dependencies like rollup-plugin-typescript and rollup-plugin-node-resolve ensure smooth integration with existing JavaScript ecosystems.
The difference between 2.15.1 and 2.15.2 is subtle but important. While the list of dev dependencies remains identical, crucial differences are detectable in the dist object, specifically fileCount and unpackedSize. Version 2.15.2 has a fileCount of 13 and an unpackedSize of 967730, While the older version has fileCount of 16 and unpackedSize of 985680. This suggests that version 2.15.2 ships with fewer files and a slightly smaller footprint, potentially indicating bug fixes, build optimizations, or removal of redundant resources. Developers upgrading should expect a lighter package. The release date also highlights a quick turnaround, with 2.15.2 released shortly after 2.15.1, suggesting the patch addresses immediate issues.
All the vulnerabilities related to the version 2.15.2 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