Svelte version 3.23.2 introduces subtle but potentially impactful changes compared to its predecessor, 3.23.1, targeting developers seeking enhanced performance and refined tooling. A key upgrade involves the code-red dev dependency, moving from version 0.1.1 to 0.1.2, likely addressing internal code generation improvements and possibly bug fixes related to code transformations. Furthermore, puppeteer, a critical tool for end-to-end testing, sees a significant jump from version 1.19.0 to 2.1.1, bringing newer browser automation capabilities, improved stability, and potentially support for newer browser features valuable for comprehensive testing.
The update includes minor changes in the distribution files, with the file count increasing from 201 to 203 and the unpacked size growing from 3,134,534 bytes to 3,146,510 bytes. These changes suggest additions, refactorings, or optimization which would affect the generated code. Developers should consider this if they have storage constraints. While the core functionality remains consistent, these dependency upgrades can influence the development workflow through more robust testing and potentially more efficient code generation. This release ensures compatibility with the latest browser technologies, making it a valuable upgrade for developers prioritizing cutting-edge testing and code generation.
All the vulnerabilities related to the version 3.23.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