CVE-2024-23331: Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem

Published Jan 19, 2024
·
Updated

### Summary [Vite dev server option](https://vitejs.dev/config/server-options.html#server-fs-deny) `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** 1. 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/ 2. Created dummy secret files, e.g. `custom.secret` and `production.pem` 3. Populated `vite.config.js` with ```javascript export default { server: { fs: { deny: ['.env', '.env.*', '*.{crt,pem}', 'custom.secret'] } } } ``` **Reproduction** 1. `curl -s http://20.12.242.81:5173/@fs//` - Descriptive error page reveals absolute filesystem path to project root 2. `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 3. `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** ![Screenshot 2024-01-19 022736](https://user-images.githubusercontent.com/907968/298020728-3a8d3c06-fcfd-4009-9182-e842f66a6ea5.png) ### 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

Affected Software

9 affected componentsFixes available
npm/vite>=5.0.0<=5.0.11
5.0.12
npm/vite>=4.0.0<=4.5.1
4.5.2
npm/vite>=3.0.0<=3.2.7
3.2.8
npm/vite>=2.7.0<=2.9.16
2.9.17
All of the following
Any of the following
vitejs Vite Node.js>=2.7.0<2.9.17
vitejs Vite Node.js>=3.0.0<3.2.8
vitejs Vite Node.js>=4.0.0<4.5.2
vitejs Vite Node.js>=5.0.0<5.0.12
Microsoft Windows

Event History

Jan 19, 2024
CVE Published
via MITRE·07:43 PM
Data Sourced
via MITRE·07:43 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:58 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-23331?

CVE-2024-23331 is a vulnerability that could allow bypassing the server.fs.deny option on case-insensitive file systems, particularly affecting Windows servers.

2

How do I fix CVE-2024-23331?

To fix CVE-2024-23331, upgrade Vite to version 2.9.17, 3.2.8, 4.5.2, or 5.0.12 or later, depending on your current version.

3

What systems are affected by CVE-2024-23331?

CVE-2024-23331 primarily affects servers hosted on Windows with case-insensitive file systems.

4

Is there a workaround for CVE-2024-23331 before I can upgrade?

A temporary workaround for CVE-2024-23331 is to restrict access to sensitive files manually on Windows servers until an upgrade can be performed.

5

Which versions of Vite are vulnerable to CVE-2024-23331?

Versions of Vite between 2.7.0 and 2.9.16, 3.0.0 and 3.2.7, 4.0.0 and 4.5.1, and 5.0.0 and 5.0.11 are vulnerable to CVE-2024-23331.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203