Svelte 0.2.0 represents an incremental update to the fledgling "magical disappearing UI framework," building upon version 0.1.1. Both versions share a common foundation, including core dependencies like acorn, magic-string, estree-walker, and locate-character, crucial for Svelte's compilation process. The development dependencies, used for testing and building the library itself, also remain largely consistent, indicating a stable development environment across both releases.
The key enhancement in version 0.2.0 lies in the introduction of console-group as a new development dependency. This suggests improvements in the developer experience, likely focusing on enhanced console output during development and debugging. Developers might see more structured and organized console logs, making it easier to trace errors and understand the behavior of Svelte components. While not a groundbreaking change, this addition points to an ongoing effort to refine the development workflow.
For developers considering Svelte, both versions offer a promising approach to UI development, compiling components into highly efficient vanilla JavaScript. The consistent development dependencies between the two versions signal a degree of reliability and maturity, even at these early stages. The addition of console-group in 0.2.0 could be a minor but appreciated enhancement for debugging and understanding component behavior, making it a slightly preferable choice for new projects.
All the vulnerabilities related to the version 0.2.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