-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): update dependency vitest to v2.1.9 [security] #153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-vitest-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
27b6531 to
dcef412
Compare
dcef412 to
c4565b4
Compare
c4565b4 to
03bf4af
Compare
03bf4af to
fb5d2a2
Compare
fb5d2a2 to
8c09dcc
Compare
8c09dcc to
e6b1fe1
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
e6b1fe1 to
dda0a33
Compare
dda0a33 to
a566c60
Compare
a566c60 to
f9ecc45
Compare
f9ecc45 to
359b527
Compare
359b527 to
92bffd1
Compare
92bffd1 to
4a31cb1
Compare
4a31cb1 to
4c040cc
Compare
4c040cc to
1f02e22
Compare
1f02e22 to
63c87bf
Compare
63c87bf to
b6c0a88
Compare
b6c0a88 to
4ae312a
Compare
4ae312a to
4b15974
Compare
4b15974 to
28ce3f5
Compare
28ce3f5 to
5aa5296
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.5→2.1.9GitHub Vulnerability Alerts
CVE-2025-24964
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
apioption 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
saveTestFileAPI that can edit a test file andrerunAPI that can rerun the tests. An attacker can execute arbitrary code by injecting a code in a test file by thesaveTestFileAPI and then running that file by calling thererunAPI.https://github.com/vitest-dev/vitest/blob/9a581e1c43e5c02b11e2a8026a55ce6a8cb35114/packages/vitest/src/api/setup.ts#L66-L76
PoC
calcexecutable inPATHenv var (you'll likely have it if you are running on Windows), that application will be executed.Impact
This vulnerability can result in remote code execution for users that are using Vitest serve API.
Release Notes
vitest-dev/vitest (vitest)
v2.1.9Compare Source
This release includes security patches for:
🐞 Bug Fixes
/__screenshot-error- by @hi-ogawa in #7343View changes on GitHub
v2.1.8Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.1.7Compare Source
🐞 Bug Fixes
pnpm.overridesor yarn resolutions to override theviteversion in thevitestpackage - the APIs are compatible.View changes on GitHub
v2.1.6Compare Source
🚀 Features
View changes on GitHub
v2.1.5Compare Source
🐞 Bug Fixes
dangerouslyIgnoreUnhandledErrorswithout base reporter - by @AriPerkkio in #6808 (0bf0a)unhandledRejectioneven when base reporter is not used - by @AriPerkkio in #6812 (8878b)sequence.concurrentfrom theRuntimeConfigtype - by @sheremet-va in #6880 (6af73).poll,.element,.rejects/.resolves, andlocator.*weren't awaited - by @sheremet-va in #6877 (93b67)enteror'a'- by @AriPerkkio in #6848 (487c8)🏎 Performance
View changes on GitHub
v2.1.4Compare Source
🚀 Features
This patch release includes a non-breaking feature for the experimental Browser Mode that doesn't follow SemVer. If you want to avoid picking up releases like this, make sure to pin the Vitest version in your
package.json. See npm's documentation about semver for more information.transformIndexHtml- by @sheremet-va in #6725 (16902)🐞 Bug Fixes
v=queries to setup files imports - by @sheremet-va in #6759 (b8258)toThrowErrorwith empty string parameter - by @shulaoda in #6710 (a6129)test.extendtype exports - by @hi-ogawa in #6707 (e5c38)🏎 Performance
hashto replacecreateHash- by @btea in #6703 (5d07b)View changes on GitHub
v2.1.3Compare Source
🐞 Bug Fixes
toBeNaN, toBeUndefined, toBeNull, toBeTruthy, toBeFalsy- by @hi-ogawa in #6697 (e0027)/mockServiceWorker.jsinstead of/__vitest_msw__- by @sheremet-va in #6687 (4b2ce)toMatchObjectdiff - by @hi-ogawa in #6620 (d289e)<empty line>logs when interleavingconsole.log/error- by @hi-ogawa in #6644 (9ece3)fast-globinstead oftinyglobbyin Vitest - by @sheremet-va in #6688 (70baa)🏎 Performance
View changes on GitHub
v2.1.2Compare Source
🐞 Bug Fixes
Vitest.setServerto postconfigureServerhook to enable import analysis for workspace config loading - by @hi-ogawa in #6584 (e7f35)BenchmarkResult.samplesarray to reduce memory usage - by @hi-ogawa and @AriPerkkio in #6541 (a6407)data:protocol on preview provider file upload - by @userquin in #6501 (e9821)*.astroby default - by @AriPerkkio in #6565 (f8ff7)cleanOnRerun: falseto invalidate previous results - by @AriPerkkio in #6592 (88bde)toBeDefinedwithexpect.poll- by @hi-ogawa in #6562 (f7da6)--cpu-profand--heap-profnot working by default - by @AriPerkkio in #6555 (2e4d894)beforeAllfailed - by @hi-ogawa in #6524 (fb797)onTestFinishedandonTestFailedduringretryandrepeats- by @hi-ogawa in #6609 (c5e29)--standalone- by @hi-ogawa in #6577 (d0bf8)View changes on GitHub
v2.1.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.1.0Compare Source
This release makes another big change to the Browser Mode by introducing locators API:
You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the
pageobject from@vitest/browser/context.Potential Breaking Change
vitest.config.tsorvite.config.tsinside the folder)projects/*will match anything inside theprojectsfolder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config.projects/**/*previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.🚀 Features
userEvent.uploadin playwright provider - by @sheremet-va in #6442 (cf148)--inspect- by @AriPerkkio in #6433 (0499a)--inspect-brk- by @AriPerkkio in #6434 (7ab0f)--exclude-after-remap- by @AriPerkkio in #6309 (5932a){ spy: true }instead of a factory - by @sheremet-va in #6289 (95f02)vi.advanceTimersToNextFrame- by @bnjm and @sheremet-va in #6347 (8ff63)fast-globtotinyglobby- by @SuperchupuDev in #6274 (c321a)🐞 Bug Fixes
indexfile - by @sheremet-va in #6266 (081cf)expect.getState().testPathalways returns correct path - by @sheremet-va in #6472 (ac698)vitestand@vitest/*versions don't match - by @AriPerkkio in #6317 (e662c)vitenodefor uncovered files - by @AriPerkkio in #6044 (da52d)performance.nowinstead ofDate.nowfor duration - by @LuciNyan in #6382 (fe489)toMatchInlineSnapshotupdates at the same location - by @hi-ogawa in #6332 (1606f)typecheck.includeoverlaps withinclude- by @sheremet-va in #6256 (153ff)View changes on GitHub
Configuration
📅 Schedule: Branch creation - "" (UTC), 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.
This PR has been generated by Mend Renovate using a curated preset maintained by
. View repository job log here