Vite has an `server.fs.deny` bypass with an invalid `request-target`
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.2.6, 6.1.5, 6.0.15, 5.4.18, 4.5.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub, 1 Nuclei template
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
Vite 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- vitejs vite
From 6.2.0 · fixed in 6.2.6; From 6.1.0 · fixed in 6.1.5; From 6.0.0 · fixed in 6.0.15; From 5.0.0 · fixed in 5.4.18; fixed in 4.5.13
- vitenpm
From 6.2.0 · fixed in 6.2.6
- vitenpm
From 6.1.0 · fixed in 6.1.5
- vitenpm
From 6.0.0 · fixed in 6.0.15
- vitenpm
From 5.0.0 · fixed in 5.4.18
- vitenpm
fixed in 4.5.13