@sveltejs/kit has unescaped error message included on error page
What fixes it
- 2.8.3@sveltejs/kit, npmGitHub
npm install @sveltejs/kit@2.8.3
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
Summary
The static error.html template for errors contains placeholders that are replaced without escaping the content first.
Details
From https://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
Text from GitHub Advisory Database
Affected versions 3
- @sveltejs/kit, npm< 2.8.3GitHub
- kitaffected: < 2.8.3CVE List
- @sveltejs/kit, npmfrom first release, fixed in 2.8.3OSV
References 7
- github.com/sveltejs/kit/releases/tag/%40sveltejs%2Fkit%402.8.3Fixvia GitHub
- github.com/sveltejs/kit/commit/134e36343ef57ed7e6e2b3bb9e7f05ad37865794Fixvia CVE List
- github.com/sveltejs/kit/security/advisories/GHSA-mh2x-fcqh-fmqvAdvisoryvia CVE List
- github.com/advisories/GHSA-mh2x-fcqh-fmqvAdvisoryvia GitHub
- github.com/sveltejs/kit/pull/13050Referencevia GitHub
- nvd.nist.gov/vuln/detail/CVE-2024-53262Referencevia GitHub
- kit.svelte.dev/docs/errorsReferencevia CVE List