HighGHSA-353f-5xf4-qw67CVE-2023-34092

Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)

Published 6 Jun 2023 · Updated 10 Sept 2026

Affected packages

vitenpm
Affected
<2.9.16
Fixed in
2.9.16
Update to the fixed version for your release line, for example:npm install vite@2.9.16
vitenpm
Affected
>=3.0.2 <3.2.7
Fixed in
3.2.7
Update to the fixed version for your release line, for example:npm install vite@3.2.7
vitenpm
Affected
>=4.0.0 <4.0.5
Fixed in
4.0.5
Update to the fixed version for your release line, for example:npm install vite@4.0.5
vitenpm
Affected
>=4.1.0 <4.1.5
Fixed in
4.1.5
Update to the fixed version for your release line, for example:npm install vite@4.1.5
vitenpm
Affected
>=4.2.0 <4.2.3
Fixed in
4.2.3
Update to the fixed version for your release line, for example:npm install vite@4.2.3
vitenpm
Affected
>=4.3.0 <4.3.9
Fixed in
4.3.9
Update to the fixed version for your release line, for example:npm install vite@4.3.9

Details

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.

Proof Images: !proof-1\n!proof-2

Is GHSA-353f-5xf4-qw67 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vite, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.