Skip to content
Fencer Intel
high 7.5

CVE-2024-23331 json

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

published 2y ago modified 24d ago also EUVD-2024-0322 , GHSA-c24v-8rfc-w8vw

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Vite is a frontend tooling framework for javascript. The 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 CVE-2023-34092 -- with surface area reduced to hosts having case-insensitive filesystems. Since `picomatch` defaults to case-sensitive glob matching, but the file server doesn't discriminate; a blacklist bypass is possible. By requesting raw filesystem paths using augmented casing, the matcher derived from `config.server.fs.deny` fails to block access to sensitive files. This issue has been addressed in vite@5.0.12, vite@4.5.2, vite@3.2.8, and vite@2.9.17. Users are advised to upgrade. Users unable to upgrade should restrict access to dev servers.

Patch / fix

  • npm vite 2.9.17, 3.2.8, 4.5.2, 5.0.12
  • vitejs vite 2.9.17, 3.2.8, 4.5.2, 5.0.12
  • velociraptor openSUSE Tumbleweed 0.7.0.4.git142.862ef23-1.1

opensuse advisories openSUSE-SU-2025:14663-1

Is CVE-2024-23331 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 Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/vitejs/vite/security/advisories/GHSA-c24v-8rfc-w8vw 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.7.0, <2.9.17
>=3.0.0, <3.2.8
>=4.0.0, <4.5.2
>=5.0.0, <5.0.12
2.9.17
3.2.8
4.5.2
5.0.12

Affected products

  • vitejs vite

Classification

Weakness
  • CWE-178 Improper Handling of Case Sensitivity
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-284 Improper Access Control

References

Sources

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.