Svelte 2.12.0 is a minor release following version 2.11.0 of the "magical disappearing UI framework." Both versions share the same core description and maintain the MIT license, developed by Rich Harris. Examining the devDependencies, the list appears identical in both versions, encompassing tools like rollup for bundling, typescript for enhanced JavaScript development, eslint for code linting, and mocha for testing. This suggests that the core development dependencies and tooling remained consistent between releases.
The key differences lie in the dist section. While both versions have the same fileCount of 14, the unpackedSize is marginally smaller in 2.12.0 (2603938 bytes) compared to 2.11.0 (2605168 bytes). This indicates slight optimizations or reductions in the overall package size. The releaseDate also provides a timeline, with 2.12.0 being released on August 23, 2018, shortly after 2.11.0 on August 15, 2018.
For developers, this suggests a focus on stability and minor improvements rather than major feature additions. The consistent devDependencies ensure a familiar development environment for those upgrading. The reduced package size, however small, contributes to faster download and installation times. Given the close release dates, the update likely addresses bug fixes or performance tweaks identified in the previous version, promising a slightly smoother experience for Svelte users.
All the vulnerabilities related to the version 2.12.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