Vite dev server option server.fs.deny
did not deny requests for patterns with directories. An example of such a pattern is /foo/**/*
.
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.
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
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
.
matchBase: true
, you can get any file under .git/
(config, HEAD, etc).matchBase: false
, you cannot get any file under .git/
(config, HEAD, etc).{ "nvd_published_at": "2024-04-04T16:15:09Z", "cwe_ids": [ "CWE-200", "CWE-284" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2024-04-03T16:46:17Z" }