Description
Summary
The contents of files in the project root that are denied by a file matching pattern can be returned to the browser.
Impact
Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.
Only files that are under project root and are denied by a file matching pattern can be bypassed.
- Examples of file matching patterns:
.env,.env.*,*.{crt,pem},**/.env - Examples of other patterns:
**/.git/**,.git/**,.git/**/*
Details
server.fs.deny can contain patterns matching against files (by default it includes .env, .env.*, *.{crt,pem} as such patterns).
These patterns were able to bypass for files under root by using a combination of slash and dot (/.).
PoC
npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env/. http://localhost:5173
Summary
The contents of files in the project root that are denied by a file matching pattern can be returned to the browser.
Impact
Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.
Only files that are under project root and are denied by a file matching pattern can be bypassed.
- Examples of file matching patterns:
.env,.env.*,*.{crt,pem},**/.env - Examples of other patterns:
**/.git/**,.git/**,.git/**/*
Details
server.fs.deny can contain patterns matching against files (by default it includes .env, .env.*, *.{crt,pem} as such patterns).
These patterns were able to bypass for files under root by using a combination of slash and dot (/.).
PoC
npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env/. http://localhost:5173
Impact Assessment
This medium-severity vulnerability could be exploited under certain conditions to compromise security controls or access sensitive information. Should be addressed in a timely manner.
Probability of exploitation in the next 30 days · more likely than 66.5% of all CVEs.
Quick Facts
Weakness Types
CVSS v3.1 Metrics Breakdown
How to Fix This Vulnerability
Remediation Steps
- 1Upgrade the package to version 6.3.4, 6.2.7, 6.1.6, 5.4.19, 4.5.14 or later
- 2Review and audit affected systems for potential exploitation
- 3Implement additional security controls if immediate patching is not possible
- 4Monitor for suspicious activity related to this vulnerability
Mitigation Strategies
Immediate Patching
HighApply security patches to version 6.3.4, 6.2.7, 6.1.6, 5.4.19, 4.5.14 immediately
Network Segmentation
MediumIsolate affected systems from untrusted networks until patching is complete
Monitoring and Detection
MediumImplement enhanced monitoring for exploitation attempts and unusual behavior