Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock
vitest-dev vitest · @vitest mocker
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @vitest/mocker npm |
|
|
| vitest npm |
|
vitest-dev vitest · @vitest mocker
| Product | Affected | Fixed in |
|---|---|---|
| @vitest/mocker npm |
|
|
| vitest npm |
|
|
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.
From the CVE record · GitHub_M
The public mockerPlugin and standalone interceptorPlugin do not check redirect targets against Vite's file-serving allowlist. A remote attacker who can reach an exposed development server can use its unauthenticated HMR WebSocket to read local files accessible to the server process. Vitest browser mode uses token-authenticated RPC and is not remotely unauthenticated by default.
Check npm installations of vitest or @vitest/mocker at versions >=2.1.0 <4.1.11 or >=5.0.0-beta.1 <5.0.0-rc.2.