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

chore(deps): update dependency vite to v2.9.16 [security] - autoclosed #488

Closed

renovate wants to merge 1 commit into master from renovate/npm-vite-vulnerability

Contributor

renovate bot commented May 23, 2024

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite (source)	`2.4.3` -> `2.9.16`

GitHub 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 your vite.config.js file, 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 directories

Impact

Only users explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected, and only files in the immediate Vite project root folder could be exposed.

Patches

Fixed in [email protected], [email protected], [email protected], [email protected]
And in the latest minors of the previous two majors: [email protected], [email protected]

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

Create a new latest project of vite using any package manager. (here I'm using react and vue templates for tested and pnpm)
Serve the application on dev mode using pnpm run dev.
Directly access the file from url using double forward-slash (//) (e.g: //.env, //.env.local)
Server Options fs.deny restrict successfully bypassed.

Proof Images:

Release Notes

vitejs/vite (vite)

`v2.9.16`

Please refer to CHANGELOG.md for details.

`v2.9.15`

Please refer to CHANGELOG.md for details.

`v2.9.14`

Please refer to CHANGELOG.md for details.

`v2.9.13`

Please refer to CHANGELOG.md for details.

`v2.9.12`

Please refer to CHANGELOG.md for details.

`v2.9.11`

Please refer to CHANGELOG.md for details.

`v2.9.10`

Please refer to CHANGELOG.md for details.

`v2.9.9`

Please refer to CHANGELOG.md for details.

`v2.9.8`

Please refer to CHANGELOG.md for details.

`v2.9.7`

Please refer to CHANGELOG.md for details.

`v2.9.6`

Please refer to CHANGELOG.md for details.

`v2.9.5`

Please refer to CHANGELOG.md for details.

`v2.9.4`

Please refer to CHANGELOG.md for details.

`v2.9.3`

Please refer to CHANGELOG.md for details.

`v2.9.2`

Please refer to CHANGELOG.md for details.

`v2.9.1`

Please refer to CHANGELOG.md for details.

`v2.9.0`

Please refer to CHANGELOG.md for details.

`v2.8.6`

Please refer to CHANGELOG.md for details.

`v2.8.5`

Please refer to CHANGELOG.md for details.

`v2.8.4`

Please refer to CHANGELOG.md for details.

`v2.8.3`

Please refer to CHANGELOG.md for details.

`v2.8.2`

Please refer to CHANGELOG.md for details.

`v2.8.1`

Please refer to CHANGELOG.md for details.

`v2.8.0`

Please refer to CHANGELOG.md for details.

`v2.7.13`

Please refer to CHANGELOG.md for details.

`v2.7.12`

Please refer to CHANGELOG.md for details.

`v2.7.11`

Please refer to CHANGELOG.md for details.

`v2.7.10`

Please refer to CHANGELOG.md for details.

`v2.7.9`

Please refer to CHANGELOG.md for details.

`v2.7.8`

Please refer to CHANGELOG.md for details.

`v2.7.7`

Please refer to CHANGELOG.md for details.

`v2.7.6`

Please refer to CHANGELOG.md for details.

`v2.7.5`

Please refer to CHANGELOG.md for details.

`v2.7.4`

Please refer to CHANGELOG.md for details.

`v2.7.3`

Please refer to CHANGELOG.md for details.

`v2.7.2`

Please refer to CHANGELOG.md for details.

`v2.7.1`

Please refer to CHANGELOG.md for details.

`v2.7.0`

Please refer to CHANGELOG.md for details.

`v2.6.14`

`v2.6.13`

`v2.6.12`

`v2.6.11`

`v2.6.10`

`v2.6.9`

`v2.6.8`

`v2.5.10`

`v2.5.9`

`v2.5.8`

`v2.5.7`

`v2.5.6`

`v2.4.4`

Configuration

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

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate. View repository job log here.


chore(deps): update dependency vite to v2.9.16 [security]

910aff0

renovate bot enabled auto-merge (rebase)

May 23, 2024 16:11

renovate bot changed the title ~~chore(deps): update dependency vite to v2.9.16 [security]~~ chore(deps): update dependency vite to v2.9.16 [security] - autoclosed

renovate bot closed this

auto-merge was automatically disabled

June 17, 2024 16:19

Pull request was closed

renovate bot deleted the renovate/npm-vite-vulnerability branch

June 17, 2024 16:19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment