This repository was archived by the owner on Nov 10, 2023. It is now read-only.
chore(deps): update dependency vite to v2.9.16 [security] - #27
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency vite to v2.9.16 [security]#27renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-vite-vulnerability
branch
from
June 6, 2023 04:47
d15be3b to
c3f403d
Compare
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.8.6->2.9.16GitHub Vulnerability Alerts
CVE-2022-35204
Vitejs Vite before v2.9.13 was discovered to allow attackers to perform a directory traversal via a crafted URL to the victim's service.
CVE-2023-34092
Summary
The issue involves a security vulnerability in Vite, where the server options can be bypassed using a double forward slash (
//). This vulnerability poses a potential security risk as it can allow unauthorized access to sensitive directories and files. This document outlines the steps to address and mitigate this issue. Adding Extra References : ## Steps to Fix. Update Vite:Ensure that you are using the latest version of Vite. Security issues like this are often fixed in newer releases.\n\n2. Secure the Server Configuration:In yourvite.config.jsfile, review and update the server configuration options to restrict access to unauthorized requests or directories. For example:```javascript\n // vite.config.js\n export default { server: {\n fs: {\n deny: ['private-directory'] // Restrict access to specific directoriesImpact
Only users explicitly exposing the Vite dev server to the network (using
--hostorserver.hostconfig option) are affected, and only files in the immediate Vite project root folder could be exposed.Patches
Fixed in vite@4.3.9, vite@4.2.3, vite@4.1.5, vite@4.0.5
And in the latest minors of the previous two majors: vite@3.2.7, vite@2.9.16
Details
Vite serve the application with under the root-path of the project while running on the dev mode. By default, vite using server options fs.deny to protected the sensitive information of the file. But, with simply double forward-slash, we can bypass this fs restriction.
PoC
//) (e.g://.env,//.env.local)fs.denyrestrict successfully bypassed.Proof Images:


Release Notes
vitejs/vite (vite)
v2.9.16Compare Source
Please refer to CHANGELOG.md for details.
v2.9.15Compare Source
Please refer to CHANGELOG.md for details.
v2.9.14Compare Source
Please refer to CHANGELOG.md for details.
v2.9.13Compare Source
Please refer to CHANGELOG.md for details.
v2.9.12Compare Source
Please refer to CHANGELOG.md for details.
v2.9.11Compare Source
Please refer to CHANGELOG.md for details.
v2.9.10Compare Source
Please refer to CHANGELOG.md for details.
v2.9.9Compare Source
Please refer to CHANGELOG.md for details.
v2.9.8Compare Source
Please refer to CHANGELOG.md for details.
v2.9.7Compare Source
Please refer to CHANGELOG.md for details.
v2.9.6Compare Source
Please refer to CHANGELOG.md for details.
v2.9.5Compare Source
Please refer to CHANGELOG.md for details.
v2.9.4Compare Source
Please refer to CHANGELOG.md for details.
v2.9.3Compare Source
Please refer to CHANGELOG.md for details.
v2.9.2Compare Source
Please refer to CHANGELOG.md for details.
v2.9.1Compare Source
Please refer to CHANGELOG.md for details.
v2.9.0Compare Source
Please refer to CHANGELOG.md for details.
Configuration
📅 Schedule: Branch creation - "" in timezone Asia/Tokyo, 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. View repository job log here.