Vitest: Servers misapply `server.fs.deny`, serving `.env`, private keys, `.git`, and the API token file
- 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 5.0.5, 1.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Vitest is a testing framework powered by Vite. From 5.0.0-beta.6 until 5.0.5, Vitest dev servers can misapply server.fs.deny because project servers replace Vite's defaults and the root server adds .vitest-secret-token after Vite compiles its matcher. An attacker who can reach an affected UI, Browser Mode, or API server can read denied project files or the fallback API token at node_modules/.vitest/.vitest-secret-token, and Browser Mode with test.projects can expose JavaScript-compatible .env values through a malicious website. This issue is fixed in version 5.0.5.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- First seen by cve.now
Affected versions
- vitest-dev vitest
From 5.0.0-beta.6 · fixed in 5.0.5
- @vitest browser
From 5.0.0-beta.6 · fixed in 5.0.5
- @vitest ui
From 5.0.0-beta.6 · fixed in 5.0.5
- vitejs vite-plus
From 1.0.0-rc.0 · fixed in 1.3.0
- @vitest/uinpm
From 5.0.0-beta.6 · fixed in 5.0.5
- @vitest/browsernpm
From 5.0.0-beta.6 · fixed in 5.0.5
- vite-plusnpm
From 1.0.0-rc.0 · fixed in 1.3.0