Skip to content
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
mainfrom
renovate/npm-vite-vulnerability
Open

chore(deps): update dependency vite to v2.9.16 [security]#27
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vite-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Sep 25, 2022

Copy link
Copy Markdown

Mend Renovate

This PR contains the following updates:

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

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

v2.9.16

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.15

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.14

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.13

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.12

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.11

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.10

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.9

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.8

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.7

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.6

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.5

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.4

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.3

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.2

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.1

Compare Source

Please refer to CHANGELOG.md for details.

v2.9.0

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


  • 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 requested a review from Hiratake as a code owner September 25, 2022 22:28
@renovate renovate Bot added 🔒problem:security セキュリティに関する問題 🤖dependencies 依存関係の更新 labels Sep 25, 2022
@renovate renovate Bot changed the title chore(deps): update dependency vite to 2.9.13 [security] chore(deps): update dependency vite to v2.9.13 [security] Mar 16, 2023
@renovate renovate Bot changed the title chore(deps): update dependency vite to v2.9.13 [security] chore(deps): update dependency vite to v2.9.16 [security] Jun 6, 2023
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from d15be3b to c3f403d Compare June 6, 2023 04:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

🤖dependencies 依存関係の更新 🔒problem:security セキュリティに関する問題

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants