Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(deps): update dependency vite to v6.2.7 [security]#738

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
cexbrayat merged 1 commit intomainfromrenovate/npm-vite-vulnerability
May 6, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovaterenovatebot commentedApr 19, 2025
edited
Loading

This PR contains the following updates:

PackageChangeAgeAdoptionPassingConfidence
vite (source)6.2.4 ->6.2.7ageadoptionpassingconfidence

GitHub Vulnerability Alerts

CVE-2025-31125

Summary

The contents of arbitrary files can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using--host orserver.host config option) are affected.

Details

  • base64 encoded content of non-allowed files is exposed using?inline&import (originally reported as?import&?inline=1.wasm?init)
  • content of non-allowed files is exposed using?raw?import

/@​fs/ isn't needed to reproduce the issue for files inside the project root.

PoC

Original report (check details above for simplified cases):

The ?import&?inline=1.wasm?init ending allows attackers to read arbitrary files and returns the file content if it exists. Base64 decoding needs to be performed twice

$ npm create vite@latest$ cd vite-project/$ npm install$ npm run dev

Example full URLhttp://localhost:5173/@​fs/C:/windows/win.ini?import&?inline=1.wasm?init

CVE-2025-31486

Summary

The contents of arbitrary files can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host orserver.host config option) are affected.

Details

.svg

Requests ending with.svg are loaded at this line.
https://github.com/vitejs/vite/blob/037f801075ec35bb6e52145d659f71a23813c48f/packages/vite/src/node/plugins/asset.ts#L285-L290
By adding?.svg with?.wasm?init or withsec-fetch-dest: script header, the restriction was able to bypass.

This bypass is only possible if the file is smaller thanbuild.assetsInlineLimit (default: 4kB) and when using Vite 6.0+.

relative paths

The check was applied before the id normalization. This allowed requests to bypass with relative paths (e.g.../../).

PoC

npm create vite@latestcd vite-project/npm installnpm run dev

send request to readetc/passwd

curl'http://127.0.0.1:5173/etc/passwd?.svg?.wasm?init'
curl'http://127.0.0.1:5173/@​fs/x/x/x/vite-project/?/../../../../../etc/passwd?import&?raw'

CVE-2025-32395

Summary

The contents of arbitrary files can be returned to the browser if the dev server is running on Node or Bun.

Impact

Only apps with the following conditions are affected.

  • explicitly exposing the Vite dev server to the network (using --host orserver.host config option)
  • running the Vite dev server on runtimes that are not Deno (e.g. Node, Bun)

Details

HTTP 1.1 spec (RFC 9112) does not allow# inrequest-target. Although an attacker can send such a request. For those requests with an invalidrequest-line (it includesrequest-target), the specrecommends to reject them with 400 or 301. The same can be said for HTTP 2 (ref1,ref2,ref3).

On Node and Bun, those requests are not rejected internally and is passed to the user land. For those requests, the value ofhttp.IncomingMessage.url contains#. Vite assumedreq.url won't contain# when checkingserver.fs.deny, allowing those kinds of requests to bypass the check.

On Deno, those requests are not rejected internally and is passed to the user land as well. But for those requests, the value ofhttp.IncomingMessage.url did not contain#.

PoC

npm create vite@latestcd vite-project/npm installnpm run dev

send request to read/etc/passwd

curl --request-target /@​fs/Users/doggy/Desktop/vite-project/#/../../../../../etc/passwd http://127.0.0.1:5173

CVE-2025-46565

Summary

The contents of files inthe projectroot that are denied by a file matching pattern can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host orserver.host config option) are affected.
Only files that are underprojectroot and are denied by a file matching pattern can be bypassed.

  • Examples of file matching patterns:.env,.env.*,*.{crt,pem},**/.env
  • Examples of other patterns:**/.git/**,.git/**,.git/**/*

Details

server.fs.deny can contain patterns matching against files (by default it includes.env,.env.*,*.{crt,pem} as such patterns).
These patterns were able to bypass for files underroot by using a combination of slash and dot (/.).

PoC

npm create vite@latestcd vite-project/cat "secret" > .envnpm installnpm run devcurl --request-target /.env/. http://localhost:5173

image
image


Release Notes

vitejs/vite (vite)

v6.2.7

Compare Source

Please refer toCHANGELOG.md for details.

v6.2.6

Compare Source

Please refer toCHANGELOG.md for details.

v6.2.5

Compare Source

Please refer toCHANGELOG.md for details.


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.


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

This PR was generated byMend Renovate. View therepository job log.

@renovaterenovatebotforce-pushed therenovate/npm-vite-vulnerability branch fromc114997 toc4330ffCompareApril 30, 2025 19:46
@renovaterenovatebot changed the titlechore(deps): update dependency vite to v6.2.6 [security]chore(deps): update dependency vite to v6.2.7 [security]Apr 30, 2025
@cexbrayatcexbrayat merged commitce03b91 intomainMay 6, 2025
52 checks passed
@renovaterenovatebot deleted the renovate/npm-vite-vulnerability branchMay 6, 2025 06:08
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@cexbrayatcexbrayatcexbrayat approved these changes

Assignees
No one assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

1 participant
@cexbrayat

[8]ページ先頭

©2009-2025 Movatter.jp