CVE-2025-31125 – vite

Package

Manager: npm
Name: vite
Vulnerable Version: >=6.2.0 <6.2.4 || >=6.1.0 <6.1.3 || >=6.0.0 <6.0.13 || >=5.0.0 <5.4.16 || >=0 <4.5.11

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: 0.09704 pctl0.92608

Details

Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` query ### 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](https://vitejs.dev/config/server-options.html#server-host)) 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`

Metadata

Created: 2025-03-31T17:31:54Z
Modified: 2025-03-31T23:32:54Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/03/GHSA-4r4m-qw57-chr8/GHSA-4r4m-qw57-chr8.json
CWE IDs: ["CWE-200", "CWE-284"]
Alternative ID: GHSA-4r4m-qw57-chr8
Finding: F039
Auto approve: 1