Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock
- 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 4.1.11, 5.0.0-rc.2
- 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 2.1.0 until 4.1.11 and 5.0.0-rc.2, the public mockerPlugin and standalone interceptorPlugin exports in packages/mocker/src/node/interceptorPlugin.ts register the vitest:interceptor:register handler on Vite's unauthenticated HMR WebSocket without validating redirect targets against the file-serving allowlist. The implementation processes event.redirect without enforcing server.fs.allow and server.fs.deny through isFileLoadingAllowed. A remote client that can reach an exposed development server can submit an opaque URL scheme preserving .. segments, causing join(server.config.root, redirectUrl.pathname) to resolve outside the project root. The plugin's load hook then returns readFile(mock.redirect, 'utf-8') as module source, disclosing local files readable by the dev-server process. Vitest browser mode uses a token-authenticated RPC and is not remotely unauthenticated by default, although the same boundary check was missing on that path. This issue is fixed in versions 4.1.11 and 5.0.0-rc.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- vitest-dev vitest
From 2.1.0 · fixed in 4.1.11; From 5.0.0-beta.1 · fixed in 5.0.0-rc.2
- @vitest mocker
From 2.1.0 · fixed in 4.1.11; From 5.0.0-beta.1 · fixed in 5.0.0-rc.2
- @vitest/mockernpm
From 2.1.0 · fixed in 4.1.11
- vitestnpm
From 2.1.0 · fixed in 4.1.11
- vitestnpm
From 5.0.0-beta.1 · fixed in 5.0.0-rc.2
- @vitest/mockernpm
From 5.0.0-beta.1 · fixed in 5.0.0-rc.2