Svelte version 3.44.2 and 3.44.1 are very similar, representing incremental updates to the Svelte compiler. Both versions share the same core functionality as a framework known for building cybernetically enhanced web apps, focusing on shifting work from the browser to the compile step for improved performance. They both rely on a suite of devDependencies including tools for linting(eslint, @typescript-eslint/eslint-plugin), testing(mocha, jsdom, c8), bundling (rollup), and typescript support.
Key differences lie in the unpacked size and releaseDate. Version 3.44.2 has an unpackedSize of 6945336, slightly larger than 3.44.1's 6944459, implying minor additions or changes to the compiled output or internal assets. Version 3.44.2 was released on 2021-11-19T12:23:24.142Z, while version 3.44.1 was released on 2021-11-01T14:03:48.006Z which means 3.44.2 is the most recent.
For developers, these versions provide a solid foundation to build user interfaces. The minor updates in 3.44.2 mean it likely contains bug fixes and small improvements, making it the preferable choice for new projects or upgrading existing ones. Svelte's approach of compiling components into highly efficient vanilla JavaScript during build time results in faster load times and better runtime performance compared to traditional virtual DOM frameworks. Developers benefit from a concise and declarative syntax, making Svelte code easy to grasp, maintain and extend. The comprehensive tooling ecosystem further enhances the development experience, ensuring code quality and efficient builds.
All the vulnerabilities related to the version 3.44.2 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