Svelte version 1.29.1 is a minor patch release following version 1.29.0 of the "magical disappearing UI framework." Examining the metadata, the core functionality and dependencies remain consistent between the two versions. Both versions share the same suite of development dependencies, including tools for testing (mocha, jsdom, nyc, codecov), linting (eslint, eslint-plugin-html, eslint-plugin-import), bundling (rollup, rollup-plugin-node-resolve, rollup-plugin-commonjs, rollup-plugin-typescript, rollup-plugin-buble, rollup-plugin-json, rollup-watch), and other utilities like css-tree, prettier, and typescript.
The key difference between these releases lies in their release dates. Version 1.29.1 was published on August 9, 2017, while version 1.29.0 was released a few days prior, on August 6, 2017. This small time gap usually signifies that Svelte 1.29.1 most likely addresses some bug fixes or minor improvements discovered shortly after the initial 1.29.0 release.
For developers considering Svelte, sticking with the latest patch version (1.29.1) is generally advisable due to the probable bug fixes and potential performance enhancements. While the changes may not be drastic, they ensure a more stable and refined development experience. Svelte, at its core, offers a unique approach to UI development, shifting work to compile time for highly performant JavaScript output, making it a worthwhile choice for building efficient web applications.
All the vulnerabilities related to the version 1.29.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