Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency vite to v6.2.3 [security] #837

Merged
merged 1 commit into from
Mar 29, 2025
Merged

chore(deps): update dependency vite to v6.2.3 [security] #837

merged 1 commit into from
Mar 29, 2025
+504 −365

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 25, 2025 •
edited
Loading

This PR contains the following updates:

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

GitHub Vulnerability Alerts

CVE-2025-30208

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

@fs denies access to files outside of Vite serving allow list. Adding ?raw?? or ?import&raw?? to the URL bypasses this limitation and returns the file content if it exists. This bypass exists because trailing separators such as ? are removed in several places, but are not accounted for in query string regexes.

PoC

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

$ echo "top secret content" > /tmp/secret.txt

# expected behaviour
$ curl "http://localhost:5173/@​fs/tmp/secret.txt"

    <body>
      <h1>403 Restricted</h1>
      <p>The request url &quot;/tmp/secret.txt&quot; is outside of Vite serving allow list.

# security bypassed
$ curl "http://localhost:5173/@&#8203;fs/tmp/secret.txt?import&raw??"
export default "top secret content\n"
//# sourceMappingURL=data:application/json;base64,eyJ2...

Release Notes

vitejs/vite (vite)

v6.2.3

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.2

Compare Source

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 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.

@netlify Netlify
Copy link

netlify bot commented Mar 25, 2025 •
edited
Loading

✅ Deploy Preview for vue-devtools-docs canceled.

Name Link
🔨 Latest commit a00eb45
🔍 Latest deploy log https://app.netlify.com/sites/vue-devtools-docs/deploys/67e7a52dbe5ad10008a8c29c

@pkg-pr-new pkg.pr.new
Copy link

pkg-pr-new bot commented Mar 25, 2025 •
edited
Loading

Open in Stackblitz

@vue/devtools-applet

npm i https://pkg.pr.new/@vue/devtools-applet@837

@vue/devtools-core

npm i https://pkg.pr.new/@vue/devtools-core@837

@vue/devtools-api

npm i https://pkg.pr.new/@vue/devtools-api@837

@vue/devtools-kit

npm i https://pkg.pr.new/@vue/devtools-kit@837

@vue/devtools

npm i https://pkg.pr.new/@vue/devtools@837

vite-plugin-vue-devtools

npm i https://pkg.pr.new/vite-plugin-vue-devtools@837

commit: 99547bf

@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from f8a7d23 to 8c878c3 Compare March 29, 2025 07:41
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 8c878c3 to a00eb45 Compare March 29, 2025 07:45
@webfansplz webfansplz merged commit 187c6b9 into main Mar 29, 2025
9 checks passed
@webfansplz webfansplz deleted the renovate/npm-vite-vulnerability branch March 29, 2025 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@webfansplz