Svelte 2.16.1 is a minor patch release following version 2.16.0 of this "magical disappearing UI framework". Svelte remains committed to providing a streamlined development experience, as underscored by its focus on compiling away into highly optimized vanilla JavaScript during build time, leading to smaller bundle sizes and faster performance in the browser.
Examining the metadata, the core functionalities described by name and description remain consistent between the two versions. The significant changes are more subtle, primarily within the distribution details and release timing. Version 2.16.1, released on February 8th, 2019, has a slightly larger footprint with a fileCount of 15 and an unpackedSize of 981534 bytes, compared to version 2.16.0's fileCount of 13 and unpackedSize of 967999 bytes which was released on December 16th, 2018. These modest differences hint at possible bug fixes, performance tweaks or documentation updates implemented in the newer patch, without altering the core API or introducing new features.
Developers using Svelte can expect a smooth transition between these versions, especially when adhering to semantic versioning practices. The consistent devDependencies list reflects a stable development environment, using familiar tools like Rollup, TypeScript, ESLint and Prettier. While the specific alterations triggering the increased size may be minimal, upgrading to 2.16.1 ensures that developers benefit from any refinements and potential bug resolutions present in the newer patch. For those focused on minimizing bundle size, it's worthwhile to investigate the exact nature of the increased size to ensure optimal performance for their Svelte applications.
All the vulnerabilities related to the version 2.16.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