NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

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

highCVSS 3.1 7.5GHSA-c24v-8rfc-w8vw

Summary Vite dev server option 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.

Published Jan 19, 2024

Affected packages

vite

Ecosystem
npm
Affected
>= 2.7.0, <= 2.9.16
Fixed in
2.9.17
Check
npm ls vite

vite

Ecosystem
npm
Affected
>= 3.0.0, <= 3.2.7
Fixed in
3.2.8
Check
npm ls vite

vite

Ecosystem
npm
Affected
>= 4.0.0, <= 4.5.1
Fixed in
4.5.2
Check
npm ls vite

vite

Ecosystem
npm
Affected
>= 5.0.0, <= 5.0.11
Fixed in
5.0.12
Check
npm ls vite

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

Vite dev server option 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 [email protected], [email protected], [email protected], [email protected]

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.
  2. npm run dev -- --host 0.0.0.0
  3. Publicly accessible for the time being here: http://20.12.242.81:5173/
  4. Created dummy secret files, e.g. custom.secret and production.pem
  5. Populated vite.config.js with
export default { server: { fs: { deny: ['.env', '.env.*', '*.{crt,pem}', 'custom.secret'] } } }

Reproduction

  1. curl -s http://20.12.242.81:5173/@fs//
  2. Descriptive error page reveals absolute filesystem path to project root
  3. curl -s http://20.12.242.81:5173/@fs/C:/Users/darbonzo/Desktop/vite-project/vite.config.js
  4. Discoverable configuration file reveals locations of secrets
  5. curl -s http://20.12.242.81:5173/@fs/C:/Users/darbonzo/Desktop/vite-project/custom.sEcReT
  6. Secrets are directly accessible using case-augmented version of filename

Proof Screenshot 2024-01-19 022736

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

Credited to dariushoule.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries