Svelte 3.22.1 is a minor patch release following version 3.22.0, both iterations of the "cybernetically enhanced web apps" framework. Examining the package data, the core development dependencies remain consistent between the two versions, indicating no significant overhauls in tooling or build processes. This suggests the updates are likely focused on bug fixes, performance tweaks, or minor feature enhancements rather than breaking changes or substantial new capabilities.
For developers, the key takeaway is stability. The consistent dependency list implies that upgrading from 3.22.0 to 3.22.1 should be seamless, minimizing the risk of compatibility issues within existing projects. Notably, the unpacked size increased slightly from 3,134,142 bytes to 3,134,317 suggesting subtle adjustments to the codebase or assets. The release date difference of a few hours on the same day suggests some urgent fixes were needed on the previous version. The consistent development dependencies highlight Svelte's commitment to a stable development environment with tools like Rollup, TypeScript, and ESLint ensuring code quality and efficient bundling. While the changes are incremental, this patch release contributes to the overall reliability and refinement of the Svelte framework, reinforcing its suitability for building performant and maintainable web applications.
All the vulnerabilities related to the version 3.22.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