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

> Attackers can bypass file access restrictions on case-insensitive systems to read sensitive files via case-augmented paths.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-c24v-8rfc-w8vw, MINI-67fx-6233-979c

## What is CVE-2024-23331?

CVE-2024-23331 is a high-severity path traversal vulnerability in vitejs vite, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

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

## Which versions are affected by CVE-2024-23331?

8 open source packages ship an affected version, including vite. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vite` | npm | From 2.7.0 | 2.9.17 |
| `vite` | npm | From 2.7.0 | 2.9.17 |
| `vite` | npm | From 3.0.0 | 3.2.8 |
| `vite` | npm | From 3.0.0 | 3.2.8 |
| `vite` | npm | From 4.0.0 | 4.5.2 |
| `vite` | npm | From 4.0.0 | 4.5.2 |
| `vite` | npm | From 5.0.0 | 5.0.12 |
| `vite` | npm | From 5.0.0 | 5.0.12 |

Products: Vitejs Vite.

## How do I fix CVE-2024-23331?

Upgrade vite to a fixed version for your release line: 2.9.17, 3.2.8, 4.5.2 or 5.0.12.

## Is CVE-2024-23331 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23331 exists.

## Other vulnerabilities in vitejs vite

- [CVE-2025-31125](https://insights.sbomify.com/CVE-2025-31125/): Vite Vitejs Improper Access Control (medium 5.3, exploited in the wild)
- [CVE-2026-53571](https://insights.sbomify.com/CVE-2026-53571/): Vite: `server.fs.deny` bypass on Windows alternate paths (high 8.2)
- [CVE-2026-39363](https://insights.sbomify.com/CVE-2026-39363/): Vite Affected by Arbitrary File Read via Vite Dev Server WebSocket (high 8.2)
- [CVE-2026-39364](https://insights.sbomify.com/CVE-2026-39364/): Vite has a `server.fs.deny` bypass with queries (high 8.2)
- [CVE-2023-34092](https://insights.sbomify.com/CVE-2023-34092/): Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//) (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23331 and fix it if it is affected.

What it is: CVE-2024-23331 is a high-severity path traversal vulnerability in vitejs vite, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23331 exists.

Affected packages and fixed versions:
- vite (npm): affected from 2.7.0; fixed in 2.9.17
- vite (npm): affected from 2.7.0; fixed in 2.9.17
- vite (npm): affected from 3.0.0; fixed in 3.2.8
- vite (npm): affected from 3.0.0; fixed in 3.2.8
- vite (npm): affected from 4.0.0; fixed in 4.5.2
- vite (npm): affected from 4.0.0; fixed in 4.5.2
- vite (npm): affected from 5.0.0; fixed in 5.0.12
- vite (npm): affected from 5.0.0; fixed in 5.0.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-23331/ (Markdown: https://insights.sbomify.com/CVE-2024-23331/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-23331
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-23331
- OSV: https://osv.dev/vulnerability/CVE-2024-23331

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-23331/
Summaries are generated and may contain mistakes; the official description above is the record.