Svelte, the "magical disappearing UI framework," saw a notable update with the release of version 0.1.0, succeeding the earlier 0.0.2. While both versions share a foundational architecture built upon dependencies like Acorn, Magic String, Estree Walker, and Locate Character for parsing and manipulating code, the update signifies development progress. Both versions list identical devDependencies, suggesting a consistent testing and tooling environment using packages jsdom, mocha, reify, eslint, node-resolve, eslint-plugin-import and rollup-plugin-node-resolve. The core development team, led by Rich Harris, continues to build on the MIT licensed base, ensuring an open and accessible framework.
The most apparent difference lies in the version number itself, moving from 0.0.2 to 0.1.0, indicating likely bug fixes and feature enhancements. Developers should note the updated releaseDate, shifting from November 20, 2016, to November 21, 2016, highlighting a very recent iteration. These frequent updates are important, particularly in such rapidly evolving framework.
Potential users will find a reliable environment thanks to the robust testing setup. While the core dependencies are the same, it is important to asses release notes attached to the version, as there is probably some bug fixing and code improvements. This makes Svelte a continuously refined choice for building performant web applications. Examining the project's GitHub repository would provide even greater insight into the specific changes and improvements introduced in version 0.1.0, aiding in informed decision-making regarding adoption.
All the vulnerabilities related to the version 0.1.0 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