SvelteKit: Build-time server-only module import guard could fail, resulting in server secrets being statically replaced in client bundle
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| sveltejs | kit | affected |
|
No data.
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. From version 3.0.0 until 3.1.1, the build-time server-only module guard did not treat src/params.js as a client entry point even though parameter matchers can run in the browser. Server-only modules imported through src/params.js could consequently enter the client bundle, where statically replaced private environment values or other server secrets could be exposed. This issue is fixed in 3.1.1. | |
| Title | SvelteKit: Build-time server-only module import guard could fail, resulting in server secrets being statically replaced in client bundle | |
| Weaknesses | CWE-200 CWE-668 |
|
| References |
| |
| Metrics |
cvssV3_1
|
No data.
No data.
No data.
No data.
No data.