Svelte, the "magical disappearing UI framework," saw a minor version update from 1.12.0 to 1.12.1 in March 2017. Both versions share a core dependency on magic-string for efficient string manipulation during compilation. The development dependencies, crucial for building and testing the framework itself, remained largely identical. These include tools for linting (eslint), bundling (rollup), testing (mocha, jsdom, nyc, codecov), and various Babel plugins to ensure compatibility across different JavaScript environments.
The quick release of 1.12.1, just a day after 1.12.0, suggests it likely contained bug fixes or minor improvements rather than significant feature additions. While the core functionality and developer tooling stayed consistent, this patch release underscores the Svelte team's commitment to rapid iteration and stability. For developers, this means upgrading from 1.12.0 to 1.12.1 should be seamless, involving minimal risk of breaking changes. The use of established tools like Rollup and Babel ensures a familiar development workflow, and the extensive suite of testing tools implies a high level of confidence in the framework's reliability. Although the specific fixes in 1.12.1 aren't detailed in the provided data, the quick turnaround suggests they addressed important, possibly user-reported issues, further enhancing the developer experience.
All the vulnerabilities related to the version 1.12.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