Skip to content

Bump vite to ^6.2.4 [SECURITY] #1706

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

Merged
merged 1 commit into from
Apr 14, 2025
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 11, 2025

This PR contains the following updates:

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

GitHub Vulnerability Alerts

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

Release Notes

vitejs/vite (vite)

v6.2.6

Compare Source

Please refer to CHANGELOG.md for details.


Configuration

📅 Schedule: Branch creation - "" in timezone 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 by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from atomiks as a code owner April 11, 2025 15:55
@renovate renovate bot added the dependencies Update of dependencies. label Apr 11, 2025
@renovate renovate bot requested a review from michaldudak as a code owner April 11, 2025 15:55
Copy link

netlify bot commented Apr 11, 2025

Deploy Preview for base-ui ready!

Name Link
🔨 Latest commit 3caeea4
🔍 Latest deploy log https://app.netlify.com/sites/base-ui/deploys/67fc9e1febecb10008f63657
😎 Deploy Preview https://deploy-preview-1706--base-ui.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged. label Apr 11, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from c4e4d5a to 8be30d1 Compare April 11, 2025 16:37
@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged. label Apr 11, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 8be30d1 to 3caeea4 Compare April 14, 2025 05:33
@mj12albert mj12albert merged commit c6b5454 into master Apr 14, 2025
22 checks passed
@mj12albert mj12albert deleted the renovate/npm-vite-vulnerability branch April 14, 2025 06:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Update of dependencies.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant