Svelte version 3.44.1 is a minor update to the popular JavaScript framework, following closely on the heels of version 3.44.0. Both versions share the core description of "Cybernetically enhanced web apps", highlighting Svelte's ability to streamline web development with its unique compiler-based approach. A key area of interest for developers lies in the devDependencies. In this area, we can find some differences between the versions: code-red was updated from version 0.2.2 to 0.2.3. Users might find this information helpful, as it indicates underlying tooling improvements and potential bug fixes. The updated version 3.44.1 has a slightly bigger unpacked size (6944459) compared to version 3.44.0 (6942238). This suggests that the newer version includes some additional code, assets, or minor adjustments. Both versions were released in a short timeframe (both in october-november 2021), reflecting an active development cycle. For developers seeking a stable and actively maintained framework for building performant web applications, Svelte 3.44.1 builds upon the solid foundation of 3.44.0, incorporating subtle refinements that contribute to a smoother development experience. Upgrading is recommended, and the package remains licensed under the MIT license.
All the vulnerabilities related to the version 3.44.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