GHSA-4r4m-qw57-chr8 Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` query

• npm vite: >= 6.2.0, < 6.2.4 → fixed in 6.2.4 • npm vite: >= 6.1.0, < 6.1.3 → fixed in 6.1.3 • npm vite: >= 6.0.0, < 6.0.13 → fixed in 6.0.13 • npm vite: >= 5.0.0, < 5.4.16 → fixed in 5.4.16 • npm vite: < 4.5.11 → fixed in 4.5.11

Summary The contents of arbitrary files can be returned to the browser. Impact Only apps explicitly exposing the Vite dev server to the network (using `--host` or `server.host` config option) are affected. Details • base64 encoded content of non-allowed files is exposed using `?inline&import` (originally reported as `?import&?inline=1.wasm?init`) • content of non-allowed files is exposed using `?raw?import` `/@fs/` isn't needed to reproduce the issue for files inside the project root. PoC Original report (check details above for simplified cases): The ?import&?inline=1.wasm?init ending allows attackers to read arbitrary files and returns the file content if it exists. Base64 decoding needs to be performed twice ``` $ npm create vite@latest $ cd vite-project/ $ npm install $ npm run dev ``` Example full URL `http://localhost:5173/@fs/C:/windows/win.ini?import&?inline=1.wasm?init`