Vite host file exposure in import analysis
vitejs vite · vitejs vite-plus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| vite npm |
|
|
vitejs vite · vitejs vite-plus
| Product | Affected | Fixed in |
|---|---|---|
| vite npm |
|
|
6.4.4| vite-plus npm |
|
|
Vite is a frontend tooling framework for JavaScript. Prior to 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3, import analysis can record a root-relative browser URL in safeModulePaths instead of the cleaned resolved module identifier. On a network-accessible, non-Windows development server, an imported project file whose URL matches an absolute host path can authorize a later raw-filesystem request for that host file, provided server.fs.deny does not block it. The request can disclose the matching file outside the project root, but it does not allow arbitrary path traversal because the host path must correspond to a project-relative URL authorized by the application graph. This issue is fixed in versions 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3.
From the CVE record · GitHub_M
Vite import analysis can authorize a raw-filesystem request for a host file outside the project root. On a network-accessible, non-Windows development server, this can disclose the file if an imported project file’s URL matches its absolute host path and server.fs.deny does not block the request. The issue does not allow arbitrary path traversal.
Check npm vite versions below 6.4.4, 7.0.0–7.3.6, 8.0.0–8.1.5, 8.2.0–8.2.3, or 8.3.0–8.3.2, and npm vite-plus versions below 1.1.0.