cve/2023/CVE-2023-34092.md

### [CVE-2023-34092](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-34092)
![](https://img.shields.io/static/v1?label=Product&message=vite&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3D%20%3C%202.9.16%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-200%3A%20Exposure%20of%20Sensitive%20Information%20to%20an%20Unauthorized%20Actor&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-50%3A%20Path%20Equivalence%3A%20'%2F%2Fmultiple%2Fleading%2Fslash'&color=brighgreen)

### Description

Vite provides frontend tooling. Prior to versions 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, and 4.3.9, Vite Server Options (`server.fs.deny`) can be bypassed using double forward-slash (//) allows any unauthenticated user to read file from the Vite root-path of the application including the default `fs.deny` settings (`['.env', '.env.*', '*.{crt,pem}']`). 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. This issue is fixed in vite@4.3.9, vite@4.2.3, vite@4.1.5, vite@4.0.5, vite@3.2.7, and vite@2.9.16.

### POC

#### Reference
- https://github.com/vitejs/vite/security/advisories/GHSA-353f-5xf4-qw67

#### Github
- https://github.com/FlapyPan/test-cve-2023-34092
- https://github.com/nomi-sec/PoC-in-GitHub