Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 7, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) 5.4.16 -> 5.4.19 age adoption passing confidence

GitHub Vulnerability Alerts

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 or server.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 with sec-fetch-dest: script header, the restriction was able to bypass.

This bypass is only possible if the file is smaller than build.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@latest
cd vite-project/
npm install
npm run dev

send request to read etc/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 or server.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 # in request-target. Although an attacker can send such a request. For those requests with an invalid request-line (it includes request-target), the spec recommends 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 of http.IncomingMessage.url contains #. Vite assumed req.url won't contain # when checking server.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 of http.IncomingMessage.url did not contain #.

PoC

npm create vite@latest
cd vite-project/
npm install
npm 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 in the project root 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 or server.host config option) are affected.
Only files that are under project root 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 under root by using a combination of slash and dot (/.).

PoC

npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env/. http://localhost:5173

image
image


Release Notes

vitejs/vite (vite)

v5.4.19

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.18

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.17

Compare Source

Please refer to CHANGELOG.md for details.


Configuration

📅 Schedule: Branch creation - "" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 added the renovate label Apr 7, 2025
@renovate renovate bot requested a review from a team as a code owner April 7, 2025 02:23
@renovate renovate bot requested review from chihiro-adachi and tasshi-me and removed request for a team April 7, 2025 02:23
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 7 times, most recently from 8d624c9 to b125fe2 Compare April 12, 2025 18:52
@renovate renovate bot changed the title chore(deps): update dependency vite to v5.4.17 [security] chore(deps): update dependency vite to v5.4.18 [security] Apr 12, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 12 times, most recently from d28ba64 to 7c4285b Compare April 17, 2025 21:33
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 5 times, most recently from 031009c to f57caf9 Compare April 28, 2025 00:46
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 4 times, most recently from 4d20d8c to a164513 Compare July 4, 2025 19:03
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 4 times, most recently from 5a855c4 to de295c2 Compare July 15, 2025 20:52
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 3 times, most recently from 6552b65 to c1bb25a Compare July 27, 2025 17:55
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 6 times, most recently from 7dcf389 to 4ff5d35 Compare August 12, 2025 14:50
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 3 times, most recently from 680abe9 to d8914ef Compare August 20, 2025 23:23
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 7 times, most recently from bdb6b03 to e422a26 Compare August 27, 2025 22:12
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from e422a26 to 0e3f5b0 Compare August 31, 2025 13:45
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 0e3f5b0 to ec5b704 Compare August 31, 2025 17:38
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