chore(deps): update vue to v3.2.8 [security] #53

renovate · 2023-06-06T04:46:24Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite (source)	`3.0.3` -> `3.2.8`

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

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:

CVE-2024-23331

Summary

Vite dev server option server.fs.deny can be bypassed on case-insensitive file systems using case-augmented versions of filenames. Notably this affects servers hosted on Windows.

This bypass is similar to https://nvd.nist.gov/vuln/detail/CVE-2023-34092 -- with surface area reduced to hosts having case-insensitive filesystems.

Patches

Fixed in vite@5.0.12, vite@4.5.2, vite@3.2.8, vite@2.9.17

Details

Since picomatch defaults to case-sensitive glob matching, but the file server doesn't discriminate; a blacklist bypass is possible.

See picomatch usage, where nocase is defaulted to false: https://github.com/vitejs/vite/blob/v5.1.0-beta.1/packages/vite/src/node/server/index.ts#L632

By requesting raw filesystem paths using augmented casing, the matcher derived from config.server.fs.deny fails to block access to sensitive files.

PoC

Setup

Created vanilla Vite project using npm create vite@latest on a Standard Azure hosted Windows 10 instance.
- npm run dev -- --host 0.0.0.0
- Publicly accessible for the time being here: http://20.12.242.81:5173/
Created dummy secret files, e.g. custom.secret and production.pem
Populated vite.config.js with

export default { server: { fs: { deny: ['.env', '.env.*', '*.{crt,pem}', 'custom.secret'] } } }

Reproduction

curl -s http://20.12.242.81:5173/@fs//
- Descriptive error page reveals absolute filesystem path to project root
curl -s http://20.12.242.81:5173/@fs/C:/Users/darbonzo/Desktop/vite-project/vite.config.js
- Discoverable configuration file reveals locations of secrets
curl -s http://20.12.242.81:5173/@fs/C:/Users/darbonzo/Desktop/vite-project/custom.sEcReT
- Secrets are directly accessible using case-augmented version of filename

Proof

Impact

Who

Users with exposed dev servers on environments with case-insensitive filesystems

What

Files protected by server.fs.deny are both discoverable, and accessible

Release Notes

vitejs/vite (vite)

chore(deps): update vue to v3.2.8 [security] #53

Are you sure you want to change the base?

chore(deps): update vue to v3.2.8 [security] #53

Conversation

renovate bot commented Jun 6, 2023 • edited Loading

GitHub Vulnerability Alerts

Summary

Impact

Patches

Details

PoC

Summary

Patches

Details

PoC

Impact

Release Notes

Main Changes

Multiple Entries for Library Mode

build.modulePreload options

Include Duplicate Assets in the Manifest

Customizable ErrorOverlay

Features

Bug Fixes

Previous Changelogs

3.2.0-beta.4 (2022-10-24)

3.2.0-beta.3 (2022-10-20)

3.2.0-beta.2 (2022-10-14)

3.2.0-beta.1 (2022-10-10)

3.2.0-beta.0 (2022-10-05)

Main Changes

Features

Bug Fixes

Previous Changelogs

3.1.0-beta.2 (2022-09-02)

3.1.0-beta.1 (2022-08-29)

3.1.0-beta.0 (2022-08-25)

Configuration

renovate bot commented Jan 19, 2024

⚠ Artifact update problem

File name: pnpm-lock.yaml

renovate bot commented Jun 6, 2023 •

edited

Loading

`build.modulePreload` options