Svelte 3.14.0 introduces subtle but important changes compared to version 3.13.0. Both versions share the core purpose of building "Cybernetically enhanced web apps," boasting a rich set of developer dependencies for testing, linting, and bundling. Key tools like Rollup, TypeScript, ESLint, and Mocha are consistently used across both versions, ensuring a robust development environment.
A notable difference lies in the updated code-red dependency, moving from version 0.0.19 in 3.13.0 to 0.0.20 in 3.14.0. While seemingly minor, such patch updates often include bug fixes or performance enhancements crucial for compiler optimization. The periscopic dependency saw a similar bump from 2.0.0 to 2.0.1. These changes likely refine Svelte's reactivity analysis and dependency tracking.
Furthermore, the dist object reveals alterations in the packaged size and file count. Svelte 3.14.0 contains 252 files with an unpacked size of 3023438 bytes, slightly larger than the 205 files and 3010104 bytes in version 3.13.0. This suggests that the latest release may include new features, enhancements, or additional assets. Developers should be aware of the potential impact on bundle sizes and initial load times. The release dates also show that version 3.14.0 was released approximately one day after the other.
All the vulnerabilities related to the version 3.14.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