You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to vulnerable library: /node_modules/@sveltejs/kit/package.json
Dependency Hierarchy:
❌ kit-1.0.0-next.201.tgz (Vulnerable Library)
Found in base branch: master
Vulnerability Details
The SvelteKit framework offers developers an option to create simple REST APIs. This is done by defining a +server.js file, containing endpoint handlers for different HTTP methods. SvelteKit provides out-of-the-box cross-site request forgery (CSRF) protection to its users. The protection is implemented at kit/src/runtime/server/respond.js. While the implementation does a sufficient job of mitigating common CSRF attacks, the protection can be bypassed in versions prior to 1.15.2 by simply specifying an upper-cased Content-Type header value. The browser will not send uppercase characters, but this check does not block all expected CORS requests. If abused, this issue will allow malicious requests to be submitted from third-party domains, which can allow execution of operations within the context of the victim's session, and in extreme scenarios can lead to unauthorized access to users’ accounts. This may lead to all POST operations requiring authentication being allowed in the following cases: If the target site sets SameSite=None on its auth cookie and the user visits a malicious site in a Chromium-based browser; if the target site doesn't set the SameSite attribute explicitly and the user visits a malicious site with Firefox/Safari with tracking protections turned off; and/or if the user is visiting a malicious site with a very outdated browser. SvelteKit 1.15.2 contains a patch for this issue. It is also recommended to explicitly set SameSite to a value other than None on authentication cookies especially if the upgrade cannot be done in a timely manner.
CVE-2023-29008 - High Severity Vulnerability
Vulnerable Library - kit-1.0.0-next.201.tgz
This is the [SvelteKit](https://kit.svelte.dev) framework and CLI.
Library home page: https://registry.npmjs.org/@sveltejs/kit/-/kit-1.0.0-next.201.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@sveltejs/kit/package.json
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
The SvelteKit framework offers developers an option to create simple REST APIs. This is done by defining a
+server.js
file, containing endpoint handlers for different HTTP methods. SvelteKit provides out-of-the-box cross-site request forgery (CSRF) protection to its users. The protection is implemented atkit/src/runtime/server/respond.js
. While the implementation does a sufficient job of mitigating common CSRF attacks, the protection can be bypassed in versions prior to 1.15.2 by simply specifying an upper-casedContent-Type
header value. The browser will not send uppercase characters, but this check does not block all expected CORS requests. If abused, this issue will allow malicious requests to be submitted from third-party domains, which can allow execution of operations within the context of the victim's session, and in extreme scenarios can lead to unauthorized access to users’ accounts. This may lead to all POST operations requiring authentication being allowed in the following cases: If the target site setsSameSite=None
on its auth cookie and the user visits a malicious site in a Chromium-based browser; if the target site doesn't set theSameSite
attribute explicitly and the user visits a malicious site with Firefox/Safari with tracking protections turned off; and/or if the user is visiting a malicious site with a very outdated browser. SvelteKit 1.15.2 contains a patch for this issue. It is also recommended to explicitly setSameSite
to a value other thanNone
on authentication cookies especially if the upgrade cannot be done in a timely manner.Publish Date: 2023-04-06
URL: CVE-2023-29008
CVSS 3 Score Details (8.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2023-29008
Release Date: 2023-04-06
Fix Resolution: 1.15.2
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: