Packages / @sveltejs/kit / Security
@sveltejs/kit has unescaped error message included on error page
Affected releases · @sveltejs/kit
- 2.x2.0.0 – 2.8.2Fixed in 2.8.3
- 1.x and older0.0.8 – 1.30.4No fix, no longer updated
On 2.x, the newest line:
npm install @sveltejs/kit@2.8.3Not affected
3.0.0 – 3.1.0
3 releases, latest
Affected
2.0.0 – 2.8.2
70 releases
Fixed
2.8.3 – 2.70.3
167 releases
Affected
1.0.0 – 1.30.4
128 releases
Affected
0.0.8 – 0.0.30
21 releases
Is your project affected?
Paste your package.json, or type the range you declare for @sveltejs/kit. It is read in your browser and sent nowhere.
What happens
Summary
The static error.html template for errors contains placeholders that are replaced without escaping the content first.
Details
From kit.svelte.dev/docs/errors:
error.html is the page that is rendered when everything else fails. It can contain the following placeholders: %sveltekit.status% — the HTTP status %sveltekit.error.message% — the error message
This leads to possible injection if an app explicitly creates an error with a message that contains user controlled content that ends up being something like this inside a server handle function:
error(500, '<script>alert("boom")</script>');Uncaught errors cannot be exploited like this, as they always render the message "Internal error".
Escaping the message string in the function that creates the html output can be done to improve safety for applications that are using custom errors on the server.
PoC
None provided
Impact
Only applications where user provided input is used in the Error message will be vulnerable, so the vast majority of applications will not be vulnerable