Svelte version 1.2.2 represents a minor but potentially impactful update over its predecessor, version 1.2.1. Both versions share the core characteristic of being a "magical disappearing UI framework," indicating Svelte's compile-time approach that translates components into highly efficient vanilla JavaScript during the build process, reducing runtime overhead and boosting application performance. The dependencies remain consistent across both versions, relying on magic-string for efficient source code manipulation. Svelte leverages a robust suite of development dependencies for testing, linting, building, and coverage, including tools like Rollup, ESLint, Mocha, and NYC.
A key difference lies in the release date. Version 1.2.2 was published on December 9, 2016, a day later than version 1.2.1 on December 8, 2016. While the core functionalities and dependencies remain the same, this update likely incorporates bug fixes, performance improvements, or minor feature enhancements implemented within that short timeframe, making it a worthwhile upgrade for developers seeking the most stable and optimized experience. Developers already using Svelte 1.2.1 should consider updating to 1.2.2 to benefit from these potential refinements, ensuring they are working with the latest iteration of the framework.
All the vulnerabilities related to the version 1.2.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