CVE-2023-34092 json
Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)
published 3y ago modified 28d ago also EUVD-2023-1665 , GHSA-353f-5xf4-qw67
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm vite 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, 4.3.9
- vitejs vite 3.2.7, 4.0.5, 4.1.5, 4.2.3, 4.3.9
- github.com/vitejs/vite@813ddd6 commit
- github.com/vitejs/vite#13348 pull request
Is CVE-2023-34092 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
3.15% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- github.com https://github.com/vitejs/vite/security/advisories/GHSA-353f-5xf4-qw67 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | vite | <2.9.16 >=3.0.2, <3.2.7 >=4.0.0, <4.0.5 >=4.1.0, <4.1.5 >=4.2.0, <4.2.3 >=4.3.0, <4.3.9 |
2.9.16 3.2.7 4.0.5 4.1.5 4.2.3 4.3.9 |
Affected products
- vitejs vite
Classification
References
-
github.com
/vitejs/vite/pull/13348
web, patch
-
github.com
/vitejs/vite/commit/813ddd6155c3d54801e264ba832d8347f6f66b32
web, patch
-
github.com
/vitejs/vite/security/advisories/GHSA-353f-5xf4-qw67
web, exploit, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-34092
advisory
-
github.com
/vitejs/vite
package
-
security.snyk.io
/package/npm/vite/3.2.0-beta.4
web
Sources
- CVE List CVE-2023-34092
- GitHub Advisory GHSA-353f-5xf4-qw67
- NVD CVE-2023-34092
- Maintainer advisory GHSA-353f-5xf4-qw67
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of vitejs/vite published their own advisory on GitHub. Reviewed sources take precedence over it.