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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The issue involves a security vulnerability in Vite where the server options can be bypassed using a double forward slash (//). This vulnerability poses a potential security risk as it can allow unauthorized access to sensitive directories and files.
Steps to Fix. Update Vite: Ensure that you are using the latest version of Vite. Security issues like this are often fixed in newer releases.\n2. Secure the server configuration: In your vite.config.js file, review and update the server configuration options to restrict access to unauthorized requests or directories.
Impact
Only users explicitly exposing the Vite dev server to the network (using --host or the server.host config option) are affected and only files in the immediate Vite project root folder could be exposed.\n\n### Patches\nFixed in vite@4.3.9, vite@4.2.3, vite@4.1.5, vite@4.0.5 and in the latest minors of the previous two majors, vite@3.2.7 and vite@2.9.16.
Details
Vite serves the application with under the root-path of the project while running on the dev mode. By default, Vite uses the server option fs.deny to protect sensitive files. But using a simple double forward-slash, we can bypass this restriction. \n\n### PoC\n1. Create a new latest project of Vite using any package manager. (here I'm using react and vue templates and pnpm for testing)\n2. Serve the application on dev mode using pnpm run dev.\n3. Directly access the file via url using double forward-slash (//) (e.g: //.env, //.env.local)\n4. The server option fs.deny was successfully bypassed.
Vite dev server optionserver.fs.deny can be bypassed on case-insensitive file systems using case-augmented versions of filenames. Notably this affects servers hosted on Windows.
Vite dev server optionserver.fs.deny did not deny requests for patterns with directories. An example of such a pattern is /foo/**/*.
Impact
Only apps setting a custom server.fs.deny that includes a pattern with directories, and explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.
Patches
Fixed in vite@5.2.6, vite@5.1.7, vite@5.0.13, vite@4.5.3, vite@3.2.10, vite@2.9.18
Details
server.fs.deny uses picomatch with the config of { matchBase: true }. matchBase only matches the basename of the file, not the path due to a bug (https://github.com/micromatch/picomatch/issues/89). The vite config docs read like you should be able to set fs.deny to glob with picomatch. Vite also does not set { dot: true } and that causes dotfiles not to be denied unless they are explicitly defined.
Reproduction
Set fs.deny to ['**/.git/**'] and then curl for /.git/config.
with matchBase: true, you can get any file under .git/ (config, HEAD, etc).
with matchBase: false, you cannot get any file under .git/ (config, HEAD, etc).
Starting from Vite 4.4, there is experimental support for Lightning CSS. You can opt into it by adding css.transformer: 'lightningcss' to your config file and install the optional lightningcss dev dependency. If enabled, CSS files will be processed by Lightning CSS instead of PostCSS.
esbuild 0.18 contains backwards-incompatible changes to esbuild's handling of tsconfig.json files. We think they shouldn't affect Vite users, you can review #13525 for more information.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: pnpm-lock.yaml
Scope: all 6 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/kkkaoru/openai-typescript-bot/apps/functions:
ERR_PNPM_NO_MATCHING_VERSION No matching version found for @kkkaoru/openai-models@1.2.0
This error happened while installing a direct dependency of /tmp/renovate/repos/github/kkkaoru/openai-typescript-bot/apps/functions
The latest release of @kkkaoru/openai-models is "1.1.1".
If you need the full list of all 4 published versions run "$ pnpm view @kkkaoru/openai-models versions".
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/npm-vite-vulnerability
branch
from
This PR contains the following updates:
4.2.1->4.5.3GitHub Vulnerability Alerts
CVE-2023-34092
The issue involves a security vulnerability in Vite where the server options can be bypassed using a double forward slash (
//). This vulnerability poses a potential security risk as it can allow unauthorized access to sensitive directories and files.Steps to Fix. Update Vite: Ensure that you are using the latest version of Vite. Security issues like this are often fixed in newer releases.\n2. Secure the server configuration: In your
vite.config.jsfile, review and update the server configuration options to restrict access to unauthorized requests or directories.Impact
Only users explicitly exposing the Vite dev server to the network (using
--hostor theserver.hostconfig option) are affected and only files in the immediate Vite project root folder could be exposed.\n\n### Patches\nFixed in vite@4.3.9, vite@4.2.3, vite@4.1.5, vite@4.0.5 and in the latest minors of the previous two majors, vite@3.2.7 and vite@2.9.16.Details
Vite serves the application with under the root-path of the project while running on the dev mode. By default, Vite uses the server option fs.deny to protect sensitive files. But using a simple double forward-slash, we can bypass this restriction. \n\n### PoC\n1. Create a new latest project of Vite using any package manager. (here I'm using react and vue templates and pnpm for testing)\n2. Serve the application on dev mode using
pnpm run dev.\n3. Directly access the file via url using double forward-slash (//) (e.g://.env,//.env.local)\n4. The server optionfs.denywas successfully bypassed.Proof Images:
\n
CVE-2024-23331
Summary
Vite dev server option
server.fs.denycan be bypassed on case-insensitive file systems using case-augmented versions of filenames. Notably this affects servers hosted on Windows.This bypass is similar to https://nvd.nist.gov/vuln/detail/CVE-2023-34092 -- with surface area reduced to hosts having case-insensitive filesystems.
Patches
Fixed in vite@5.0.12, vite@4.5.2, vite@3.2.8, vite@2.9.17
Details
Since
picomatchdefaults to case-sensitive glob matching, but the file server doesn't discriminate; a blacklist bypass is possible.See
picomatchusage, wherenocaseis defaulted tofalse: https://github.com/vitejs/vite/blob/v5.1.0-beta.1/packages/vite/src/node/server/index.ts#L632By requesting raw filesystem paths using augmented casing, the matcher derived from
config.server.fs.denyfails to block access to sensitive files.PoC
Setup
npm create vite@lateston a Standard Azure hosted Windows 10 instance.npm run dev -- --host 0.0.0.0custom.secretandproduction.pemvite.config.jswithReproduction
curl -s http://20.12.242.81:5173/@​fs//curl -s http://20.12.242.81:5173/@​fs/C:/Users/darbonzo/Desktop/vite-project/vite.config.jscurl -s http://20.12.242.81:5173/@​fs/C:/Users/darbonzo/Desktop/vite-project/custom.sEcReTProof
Impact
Who
What
server.fs.denyare both discoverable, and accessibleCVE-2024-31207
Summary
Vite dev server option
server.fs.denydid not deny requests for patterns with directories. An example of such a pattern is/foo/**/*.Impact
Only apps setting a custom
server.fs.denythat includes a pattern with directories, and explicitly exposing the Vite dev server to the network (using--hostorserver.hostconfig option) are affected.Patches
Fixed in vite@5.2.6, vite@5.1.7, vite@5.0.13, vite@4.5.3, vite@3.2.10, vite@2.9.18
Details
server.fs.denyuses picomatch with the config of{ matchBase: true }. matchBase only matches the basename of the file, not the path due to a bug (https://github.com/micromatch/picomatch/issues/89). The vite config docs read like you should be able to set fs.deny to glob with picomatch. Vite also does not set{ dot: true }and that causes dotfiles not to be denied unless they are explicitly defined.Reproduction
Set fs.deny to
['**/.git/**']and then curl for/.git/config.matchBase: true, you can get any file under.git/(config, HEAD, etc).matchBase: false, you cannot get any file under.git/(config, HEAD, etc).Release Notes
vitejs/vite (vite)
v4.5.3Compare Source
v4.5.2Compare Source
Please refer to CHANGELOG.md for details.
v4.5.1Compare Source
Please refer to CHANGELOG.md for details.
v4.5.0Compare Source
Please refer to CHANGELOG.md for details.
v4.4.12Compare Source
Please refer to CHANGELOG.md for details.
v4.4.11Compare Source
Please refer to CHANGELOG.md for details.
v4.4.10Compare Source
Please refer to CHANGELOG.md for details.
v4.4.9Compare Source
v4.4.8Compare Source
moduleResolution: 'node16'(#13947) (aeef670), closes #13947v4.4.7Compare Source
optimizeDeps.includenot working with paths inside packages (#13922) (06e4f57), closes #13922config.baseto vite/env path (#13941) (8e6cee8), closes #13941import.meta.envdefine replacement without quotes (#13425) (883089c), closes #13425v4.4.6Compare Source
browserHashon optimized deps during build (#13906) (0fb2340), closes #13906wsinstead of the bundled one (#13901) (049404c), closes #13901v4.4.5Compare Source
defineConfig(#13792) (c971f26), closes #13792anywithstring(#13850) (4606fd8), closes #13850v4.4.4Compare Source
vite-error-overlaywith Escape key (#13795) (85bdcda), closes #13795v4.4.3Compare Source
v4.4.2Compare Source
v4.4.1Compare Source
v4.4.0Compare Source
Experimental support for Lightning CSS
Starting from Vite 4.4, there is experimental support for Lightning CSS. You can opt into it by adding
css.transformer: 'lightningcss'to your config file and install the optionallightningcssdev dependency. If enabled, CSS files will be processed by Lightning CSS instead of PostCSS.Lightning CSS can also be used as the CSS minifier with
build.cssMinify: 'lightningcss'.See beta docs at the Lighting CSS guide.
esbuild 0.18 update
esbuild 0.18 contains backwards-incompatible changes to esbuild's handling of
tsconfig.jsonfiles. We think they shouldn't affect Vite users, you can review #13525 for more information.Templates for Solid and Qwik in create-vite
New starter templates have been added to create-vite for Solid and Qwik. Try them online at vite.new/solid-ts and vite.new/qwik-ts.
Korean Translation
Vite's docs are now translated to Korean, available at ko.vitejs.dev.
Features
fs.allow(#12863) (4a06e66), closes #12863Bug Fixes
useDefineForClassFields: falsewhen nocompilerOptions.targetis declared (#13 (7ef2472), closes #13708lastHMRTimestampof importers if the invalidated module is not a HMR bou (1143e0b), closes #13024export const { A, B }pattern (#13483) (ea1bcc9), closes #13483--host 0.0.0.0(#13438) (00ee8c1), closes #13438modulecondition (#13370) (367920b), closes #13370Previous Changelogs
4.4.0-beta.4 (2023-07-03)
See 4.4.0-beta.4 changelog
4.4.0-beta.3 (2023-06-25)
See 4.4.0-beta.3 changelog
4.4.0-beta.2 (2023-06-22)
See 4.4.0-beta.2 changelog
4.4.0-beta.1 (2023-06-21)
See 4.4.0-beta.1 changelog
4.4.0-beta.0 (2023-06-20)
See 4.4.0-beta.0 changelog
v4.3.9Compare Source
v4.3.8Compare Source
v4.3.7Compare Source
v4.3.6Compare Source
tryFsResolvefor relativenew URL(foo, import.meta.url)(#13142) (eeb0617), closes #13142esbuild.charsetwhen minify (#13190) (4fd35ed), closes #13190v4.3.5Compare Source
v4.3.4Compare Source
v4.3.3Compare Source
v4.3.2Compare Source
v4.3.1Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.