Svelte version 0.1.1 represents a minor update to the burgeoning "magical disappearing UI framework," building upon the foundation laid by version 0.1.0. Both versions share a core set of dependencies essential for Svelte's functionality: acorn for parsing, magic-string for efficient string manipulation, estree-walker for traversing syntax trees, and locate-character for character position lookups. These underpinnings enable Svelte's distinctive approach to building web applications.
The key difference lies in the developer tooling. Version 0.1.1 introduces several new devDependencies aimed at enhancing the development workflow and ensuring code quality. Notably, nyc and codecov were added for measuring test coverage, bolstering confidence in the framework's reliability. babel-register and babel-plugin-transform-es2015-modules-commonjs were included, likely to facilitate wider compatibility and potentially simplify the build process, specifically regarding module handling. Furthermore, rollup was introduced, probably to improve the bundling of the library prior to distribution, alongside babel-plugin-istanbul for instrumenting code for coverage analysis. This suggests a move towards more comprehensive testing and build processes.
For developers considering Svelte, this indicates an increased emphasis on code quality and robustness in version 0.1.1. While the core functionality remains consistent, the improved development environment promises a smoother and more reliable experience, particularly for larger projects or teams where thorough testing and consistent builds are critical. The older version is perfectly fine to start but the newer one provides more guarantees in terms of stability.
All the vulnerabilities related to the version 0.1.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