MediumGHSA-8jhw-289h-jh2gCVE-2024-31207

Vite's `server.fs.deny` did not deny requests for patterns with directories.

Published 3 Apr 2024 · Updated 10 Sept 2026

Affected packages

vitenpm

Affected: >=2.7.0 <2.9.18
Fixed in: 2.9.18

Update to the fixed version for your release line, for example:npm install vite@2.9.18

vitenpm

Affected: >=3.0.0 <3.2.10
Fixed in: 3.2.10

Update to the fixed version for your release line, for example:npm install vite@3.2.10

vitenpm

Affected: >=4.0.0 <4.5.3
Fixed in: 4.5.3

Update to the fixed version for your release line, for example:npm install vite@4.5.3

vitenpm

Affected: >=5.0.0 <5.0.13
Fixed in: 5.0.13

Update to the fixed version for your release line, for example:npm install vite@5.0.13

vitenpm

Affected: >=5.1.0 <5.1.7
Fixed in: 5.1.7

Update to the fixed version for your release line, for example:npm install vite@5.1.7

vitenpm

Affected: >=5.2.0 <5.2.6
Fixed in: 5.2.6

Update to the fixed version for your release line, for example:npm install vite@5.2.6

Details

Summary

Vite dev server option server.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).

Is GHSA-8jhw-289h-jh2g 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 signup Or connect GitHub to scan every repo

References

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