Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)
- 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 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 Nuclei template
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
Vite provides frontend tooling. Prior to versions 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, and 4.3.9, Vite Server Options (`server.fs.deny`) can be bypassed using double forward-slash (//) allows any unauthenticated user to read file from the Vite root-path of the application including the default `fs.deny` settings (`['.env', '.env.*', '*.{crt,pem}']`). Only users explicitly exposing the Vite dev server to the network (using `--host` or `server.host` config option) are affected, and only files in the immediate Vite project root folder could be exposed. This issue is fixed in vite@4.3.9, vite@4.2.3, vite@4.1.5, vite@4.0.5, vite@3.2.7, and vite@2.9.16.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- vitejs vite
fixed in 2.9.16; From 3.0.2 · fixed in 3.2.7; From 4.0.0 · fixed in 4.0.5; From 4.1.0 · fixed in 4.1.5; From 4.2.0 · fixed in 4.2.3; From 4.3.0 · fixed in 4.3.9
- vitenpm
fixed in 2.9.16
- vitenpm
From 3.0.2 · fixed in 3.2.7
- vitenpm
From 4.0.0 · fixed in 4.0.5
- vitenpm
From 4.1.0 · fixed in 4.1.5
- vitenpm
From 4.2.0 · fixed in 4.2.3
- vitenpm
From 4.3.0 · fixed in 4.3.9