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.

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 v4.2.3 [security] - autoclosed #434

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 6, 2023

Mend Renovate

This PR contains the following updates:

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

GitHub Vulnerability Alerts

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

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

Proof Images:
proof-1
proof-2


Release Notes

vitejs/vite (vite)

v4.2.3

Compare Source

Please refer to CHANGELOG.md for details.

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

@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from 854b6e7 to 3bb561a Compare June 18, 2023 08:55
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 3bb561a to b735291 Compare June 29, 2023 10:24
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from 1a67849 to a80a228 Compare July 9, 2023 10:18
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from ce11fff to f9ae36d Compare July 19, 2023 09:41
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from fbf268f to 4679c1f Compare August 1, 2023 14:00
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 4679c1f to 3e261fb Compare August 9, 2023 14:38
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 3e261fb to d0408c1 Compare August 22, 2023 18:14
@renovate renovate bot changed the title chore(deps): update dependency vite to v4.2.3 [security] chore(deps): update dependency vite to v4.2.3 [security] - autoclosed Sep 14, 2023
@renovate renovate bot closed this Sep 14, 2023
@renovate renovate bot deleted the renovate/npm-vite-vulnerability branch September 14, 2023 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants