Vite has an `server.fs.deny` bypass with an invalid `request-target`
vitejs vite
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| vite npm |
|
|
vitejs vite
| Product | Affected | Fixed in |
|---|---|---|
| vite npm |
|
|
4.5.13Vite is a frontend tooling framework for javascript. Prior to 6.2.6, 6.1.5, 6.0.15, 5.4.18, and 4.5.13, the contents of arbitrary files can be returned to the browser if the dev server is running on Node or Bun. HTTP 1.1 spec (RFC 9112) does not allow # in request-target. Although an attacker can send such a request. For those requests with an invalid request-line (it includes request-target), the spec recommends to reject them with 400 or 301. The same can be said for HTTP 2. On Node and Bun, those requests are not rejected internally and is passed to the user land. For those requests, the value of http.IncomingMessage.url contains #. Vite assumed req.url won't contain # when checking server.fs.deny, allowing those kinds of requests to bypass the check. Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) and running the Vite dev server on runtimes that are not Deno (e.g. Node, Bun) are affected. This vulnerability is fixed in 6.2.6, 6.1.5, 6.0.15, 5.4.18, and 4.5.13.
From the CVE record · GitHub_M
Vite's dev server can return arbitrary file contents to a browser when running on Node or Bun and explicitly exposed to the network. A network attacker can bypass the server.fs.deny check with a request containing #; no authentication or user interaction is described.
Teams running network-exposed Vite dev servers on Node or Bun should check npm vite versions >=6.2.0 <6.2.6, >=6.1.0 <6.1.5, >=6.0.0 <6.0.15, >=5.0.0 <5.4.18, and <4.5.13.