Skip to main content
Public proof of conceptFix available

CVE-2023-34092

A public proof of concept exists; no exploitation attested.

  • Published2023-06-01
  • Fixed in4.3.9 · 4.2.3 · 4.1.5 · 4.0.5 · 3.2.7 · 2.9.16
  • WeaknessCWE-200 · CWE-50 · CWE-706

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2023-06-0117:15CVE publishedNVD

Versions per branch

NVD · OSV
Vitejs vite
BranchAffectedFixed in
4.3≥ 4.3.0, < 4.3.94.3.9
4.2≥ 4.2.0, < 4.2.34.2.3
4.1≥ 4.1.0, < 4.1.54.1.5
4.0≥ 4.0.0, < 4.0.54.0.5
3.x≥ 3.0.2, < 3.2.73.2.7
2.9< 2.9.162.9.16
2.9= 2.9.15no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • vitejs vite
    Affected
    • = < 2.9.16no fix stated
    • = >= 3.0.2, < 3.2.7no fix stated
    • = >= 4.0.0, < 4.0.5no fix stated
    • = >= 4.1.0, < 4.1.5no fix stated
    • = >= 4.2.0, < 4.2.3no fix stated
    • = >= 4.3.0, < 4.3.9no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-06-01

Fix

  1. Update Vitejs vite to 4.3.9 · 4.2.3 · 4.1.5 · 4.0.5 · 3.2.7 · 2.9.16

Advisories and patches

Detection

read 2026-11-09 09:28 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2023-06-01
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-353f-5xf4-qw67

Frequently asked questions

What is CVE-2023-34092?

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.

Is CVE-2023-34092 actively exploited?

A proof-of-concept exploit exists for CVE-2023-34092, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2023-34092?

CVE-2023-34092 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running vite? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record