Svelte version 1.64.0 builds upon the foundation of its predecessor, 1.63.1, offering subtle yet potentially impactful enhancements for developers already using or considering this "magical disappearing UI framework." Both versions share the same core philosophy and a robust set of development dependencies, including tools for testing, linting, and bundling like mocha, eslint, and rollup. Crucially, the extensive list of devDependencies highlights Svelte's commitment to a streamlined development experience, providing developers with a comprehensive toolkit for building and maintaining Svelte applications.
The primary difference lies in the nuanced improvements and bug fixes incorporated in version 1.64.0. This is reflected in the slight increase in unpackedSize (2417546 vs 2416819), which generally suggests the addition of new features, optimizations, or code modifications. Developers might expect improved performance, better handling of edge cases, or refined compiler outputs in the newer version. Those using Typescript will note the Typescript version being locked at 2.6.1. Both versions rely on a rich ecosystem of rollup plugins, signifying a build process deeply integrated to take maximal advantage of modern Javascript features. While the core dependencies remain consistent, upgrading to 1.64.0 is recommended to benefit from the latest refinements and ensure compatibility with the evolving web development landscape. The update was released on April 17, 2018, a couple of days after the previous one.
All the vulnerabilities related to the version 1.64.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